> libMesh just hooks to PETSc and LASPACK for sparse linear algebra, > whereas deal.II has its own multithreaded linear solvers (which IIRC > were more efficient than PETSc?) for shared memory systems. If you're > running on a four-core workstation, for example, I think deal.II only > needs to store one copy of the mesh, where with libMesh you need to > either use ParallelMesh or you end up storing four copies of a > SerialMesh, one for each process. Can deal.II mix multithreading with > PETSc? If so then they've got the same advantage on clusters.
I'm actually quite interested in the answer to this question. Has *anyone* gotten PETSc working well inside a multithreaded program? It should be possible to call PETSc only from a single thread, but that kinda kills the point. Along those lines, Derek, do you know about threading in Trilinos? Our new parallel mesh and parallel algorithm implementations are clearly the answer for large-scale distributed memory machines, but when we are talking about 16+ cores per node threading has its place even inside a distributed memory mesh implementation. -Ben ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Libmesh-users mailing list Libmesh-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-users
