Hi Manav,
Extra communication can be significant. It's been awhile (~2 years) since
I've run a large problem at scale on DistributedMesh but at that time it
was about 30-40% slower than the equivalent problem on ReplicatedMesh.
Thinking back, those numbers seem really bad and I wouldn't expect it
Thanks for your comments, Derek.
We have a few different machines here, all with about 2GB per compute core. One
of the machines has 12 cores per node, and another has 20 cores per node.
Why do you say that run time will be saved with ReplicatedMesh? Is this due to
the reduced MPI communicati
A little late to the party - but we use all of the options you listed.
However: the one I would recommend is using ReplicatedMesh and just use
less cores per node in your cluster so that it fits. It will save you an
immense amount of development time... and most likely a lot of run time as
well.
