|
[Sponsors] |
[snappyHexMesh] Running snappyHexMesh in parallel - optimizing |
|
LinkBack | Thread Tools | Search this Thread | Display Modes |
December 29, 2017, 09:35 |
Running snappyHexMesh in parallel - optimizing
|
#1 |
Senior Member
Peter Hess
Join Date: Apr 2011
Location: Austria
Posts: 250
Rep Power: 17 |
Hello!
I am facing a problem here using snappyHexMesh in parallel... Steps made in my case are: - blockMesh (structured Mesh) - decompose (hierarchical) - snappyHexMesh (in parallel) Everything works actually fine. Mesh size about 400 000 Cells. The Mesh has a complex geometry in the center of the middle. The decompose sparatestheMesh allready generated by blockMesh since no snappyHexMesh avaliable yet. That means the cells are equally devided on the processors. snappyHexMesh in parallel is using the Mesh generated by blockMesh and separated by decompose. Because of the complex geometry in the middle of the Mesh, the cores loads during snappyHexMesh become different. The cores responsable for Meshing the complex geometry have more to do than the others. Cores time (sec) 4 --- 942 6 --- 881 7 --- 824 8 --- 696 9 --- 703 12 -- 877 As we can see the snappyHexMesh needs less time to 8 cores then more time! How could I let the loads (number of cells) during the snappyHexMesh changes and optimize itself to run snappyHexMesh faster (equal load for every core). Sure I can separate my blockMesh-Mesh manaully during the decompose step, but I cant separate them perfectly, cause I dont know in this step, how much cells per every core are needed. Hardware: IBM X3850 M2 - 4 X 4 cors - 3Ghz RAM 32 GB Ubuntu 17.10 - openFoam 5.0 Regards Peter Last edited by peterhess; December 31, 2017 at 17:41. |
|
January 2, 2018, 23:11 |
|
#2 |
Senior Member
Join Date: Aug 2013
Posts: 407
Rep Power: 16 |
Hi,
I had posted on this a couple of years back (https://www.cfd-online.com/Forums/op...optimally.html) Instead of hierarchical for your decomposition method, choose scotch. The advantage with scotch is that it figures out the load on each processor for you and you do not need to specify anything. While the initial decomposition (when using scotch) maybe similar to the hierarchical method, in subsequent iterations (feature/surface/region refinement steps) of snappyHexMesh, the scotch algorithm will do load balancing. To see that, you can see the processor boundaries at the start of snappyHexMesh and at the end of snappyHexMesh. They will be different. Hope this helps Cheers, Antimony |
|
January 3, 2018, 03:54 |
|
#3 |
Senior Member
Peter Hess
Join Date: Apr 2011
Location: Austria
Posts: 250
Rep Power: 17 |
Thanks Antimony
I did not notice that. I will try. Regards Peter PS: Yes u r right. Probleme solved. Thanks a lot! Last edited by peterhess; January 3, 2018 at 08:05. |
|
Tags |
snappyhexfoam decompose |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
[snappyHexMesh] Running snappyHexMesh in parallel creates new time directories | hconel | OpenFOAM Meshing & Mesh Conversion | 5 | September 27, 2022 16:20 |
Error running simpleFoam in parallel | Yuby | OpenFOAM Running, Solving & CFD | 14 | October 7, 2021 05:38 |
Error running openfoam in parallel | fede32 | OpenFOAM Programming & Development | 5 | October 4, 2018 17:38 |
[snappyHexMesh] snappyhexmesh doesn't creat mesh in parallel issue? | klausb | OpenFOAM Meshing & Mesh Conversion | 1 | March 7, 2015 12:55 |
Fluent 14.0 file not running in parallel mode in cluster | tejakalva | FLUENT | 0 | February 4, 2015 08:02 |