Dear developers, I am using libMesh for large scale parallelization. To enable the usage of 65536 processor cores, the options --with-dof-id-bytes=8 --with-processor-id-bytes=4 --with-subdomain-id-bytes=4 are already used for configuration.
However, the code 'sticks' in the following fuction: Parallel::Sort<Hilbert::HilbertIndices> sorter (communicator, sorted_hilbert_keys); sorter.sort(); in the routing MeshCommunication::find_global_indices (in file mesh_communication_global_indices.C), which is called from routine Partitioner::partition_unpartitioned_elem (in file partitioner.C). Since libMesh calls libHilbert for this sort function, is there anything should be noticed for the configuration of libHilbert when using large scale parallelization? Is that possible not to use libHilbert? If so, any efficiency degenerates? Best, Li Luo -- This message and its contents, including attachments are intended solely for the original recipient. If you are not the intended recipient or have received this message in error, please notify me immediately and delete this message from your computer system. Any unauthorized use or distribution is prohibited. Please consider the environment before printing this email. _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
