>> When I sent the following email to libmesh mail list. I met one >> problem because of the size of the email. Could you give me some >> advice regarding this problem? thanks a lot. > > It looks like it made it through eventually; just a little late.
I had to approve it based on size, and it was originally sent late US time so I didn't get to it until this morning. This is the second approval I've had to make in 24 hours, I'll see if there is > I'm not sure if you'll get an answer, though. Ben is the one > responsible for find_global_indices, and he's swamped with other > things right now. It does a parallel sort, which can be very > sensitive to MPI implementation. > It only gets used for I/O and the cost should scale more slowly than > solves, though; for large implicit 2D/3D problems it shouldn't be an > issue even on inefficient MPI implementations. Yes, this issue is bizarre indeed. The code does not even do that much communication there... You might want to compile with METHOD=pro and run it through gprof - that will give you finer grained granularity as to what the issue may actually be. Can you confirm that the problem doesn't exist on one processor? What are the details of the mesh you are using?? -Ben ------------------------------------------------------------------------------ The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
