|
[Sponsors] |
April 13, 2014, 03:30 |
from hardware to cells
|
#1 |
Senior Member
Derek Mitchell
Join Date: Mar 2014
Location: UK, Reading
Posts: 172
Rep Power: 13 |
This is the reverse of the usual question, i have the configuration already determined, the question how many cells can it cope with, aiming for a 24hr run to simulate 1 to 3 hrs. The problem space is the heat flow in insect colonies using CHTmultiregionfoam or CHTMultiregionSimpleFoam.
The config is 4 servers with dual opteron 8381 (shanghai quad core 2.5GHZ) with 2 servers with quad 8381 opteron, total 64 cores and total 64Gb memory (800mhz). Gigabit interconnect.
__________________
A CHEERING BAND OF FRIENDLY ELVES CARRY THE CONQUERING ADVENTURER OFF INTO THE SUNSET |
|
April 13, 2014, 04:36 |
|
#2 |
Retired Super Moderator
Bruno Santos
Join Date: Mar 2009
Location: Lisbon, Portugal
Posts: 10,975
Blog Entries: 45
Rep Power: 128 |
Greetings Derek,
Well, the proportions of "mesh size to RAM" may vary depending on the simulation software and the cell types in question. Because sometimes it's the vertex count that matters, others it's the face count and others is the cell count. Then it depends on the number of equations to be solved, if there are special mesh interfaces, how many subdomains there are (usually 1 subdomain per processor) and so on. In your case, it's OpenFOAM and my guess is that the mesh is made mostly of hexahedral cells... although an ant colony isn't exactly easily meshed with a purely hexahedral mesh... The rule of thumb I found a few years ago was that for the "cavity" tutorial, using blockMesh and icoFoam, the proportion seemed to be 1 GB of RAM for each 1 million cells. But as mentioned above, it's a purely hex mesh and a rather simple solver. Therefore, in your case, my suggestion is that you should do a quick study of mesh proportion to occupied RAM, using the 1 GB/Mcell as reference for building 2 cases, e.g.: one with 16 million cells and another with 32 million cells. Then launch each case for a couple of iterations, to see how much total RAM it uses in each one. Best regards, Bruno |
|
April 13, 2014, 18:03 |
|
#3 |
Senior Member
Derek Mitchell
Join Date: Mar 2014
Location: UK, Reading
Posts: 172
Rep Power: 13 |
looks like 1.5e9 bytes per 1e6 cells for the chtmultipleregionfoam.
the next thing is to fathom a reasonable value per cpu
__________________
A CHEERING BAND OF FRIENDLY ELVES CARRY THE CONQUERING ADVENTURER OFF INTO THE SUNSET |
|
April 15, 2014, 02:36 |
|
#4 |
Senior Member
Derek Mitchell
Join Date: Mar 2014
Location: UK, Reading
Posts: 172
Rep Power: 13 |
Looking at the posts it seems 50k cells is a minimum number of cells per core and 2 core per numa is probably optimal. this would give 50k x 16 x 2
or 1.6E6 so that means the range would be 1.6E6 to 40E6 cells. with the processors being 2009 era i'm thinking closer to the 1.6E6 boundary.
__________________
A CHEERING BAND OF FRIENDLY ELVES CARRY THE CONQUERING ADVENTURER OFF INTO THE SUNSET |
|
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
[snappyHexMesh] No layers in a small gap | bobburnquist | OpenFOAM Meshing & Mesh Conversion | 6 | August 26, 2015 09:38 |
[Netgen] Import netgen mesh to OpenFOAM | hsieh | OpenFOAM Meshing & Mesh Conversion | 32 | September 13, 2011 05:50 |
[snappyHexMesh] snappyHexMesh won't work - zeros everywhere! | sc298 | OpenFOAM Meshing & Mesh Conversion | 2 | March 27, 2011 21:11 |
[snappyHexMesh] snappyHexMesh aborting | Tobi | OpenFOAM Meshing & Mesh Conversion | 0 | November 10, 2010 03:23 |
physical boundary error!! | kris | Siemens | 2 | August 3, 2005 00:32 |