On Wed, Jan 27, 2010 at 11:00 AM, Kirk, Benjamin (JSC-EG311) < [email protected]> wrote:
> >> Can you confirm that the problem doesn't exist on one processor? What > are > >> the details of the mesh you are using?? > > > > You know, if we want to try repeating this ourselves, I believe Paul > > saw a relatively long find_global_indices() execution time by simply > > ultra-refining (~500K elements) a 1D mesh. I'd assumed that the key > > word there was "relatively" (we're not at all optimized for 1D, but 1D > > is still pretty fast to assemble and solve), but perhaps that case > > triggered a real problem. > > Was this on one processor? 1 and 2 on my mac. I was surprised the runtime for 2 procs was longer than 1 (on some of my smaller meshes) so I was increasing the problem size to try and rule out communcation overhead. I haven't investigated further yet. If there's anything interesting to report, I'll open up a new thread. > I think paul set a record for a 1D problem mesh > density!! > It got to machine precision though. :D Paul ------------------------------------------------------------------------------ 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
