Enable mesh partitioning on a subset of processes

[Stefano Zampini]

As it is currently implementd, mesh partitioners uses all the processes in an MPI communicator to perform the partitioning. For large core counts (say, more the 32K cores) this is an issue since the memory usage of most of the mesh partitioning packages depend on the number of processes (almost quadratically). Also, the quality of the partitioning is affected by the number of processes used.

[Chris Richardson]

Should be roughly possible by giving LocalMeshData a different communicator, but will require a fair bit of cleanup to make it happen

[Prof Garth Wells]

Issue #637 was marked as a duplicate of this issue.

[Anders Logg (Chalmers)]

Removing milestone: 1.7 (automated comment)

[sandeep shrivastava]

I find this issue useful for my need of partitioning mesh with optional argument of number of partitions and number of MPI processes.

Any progress happened in this issue? Seems like a old issue, but still open. Would be good if something might have already been updated in the past versions.