You said sparsity patterns, I read constraints... Still, I'll be happy to test it.
-Ben On Oct 26, 2012, at 6:32 PM, "Roy Stogner" <royst...@ices.utexas.edu> wrote: > > Right now, we loop over all active elements when computing sparsity > patterns. But with the attached patch, we loop over only active local > elements, then we do a round robin communication to send relevant > sparsity pattern row contributions to the processors which need them. > > Anyone have time to help me test this for correctness? It fixes the > ParallelMesh problems I was aiming to fix, and I haven't hit any > regressions yet with either ParallelMesh or SerialMesh, but it's such > a deep change that I don't feel safe committing it based on just my > preliminary tests. > > Testing for performance differences would be interesting, too. It > would be easy enough to go back to a serial code path when the mesh > isn't distributed, if the costs of looping over non-local elements > turn out to be cheaper than the costs of trading results with other > processors. > --- > Roy > <parallel_sparsity.patch> > ------------------------------------------------------------------------------ > WINDOWS 8 is here. > Millions of people. Your app in 30 days. > Visit The Windows 8 Center at Sourceforge for all your go to resources. > http://windows8center.sourceforge.net/ > join-generation-app-and-make-money-coding-fast/ > _______________________________________________ > Libmesh-devel mailing list > Libmesh-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/libmesh-devel ------------------------------------------------------------------------------ WINDOWS 8 is here. Millions of people. Your app in 30 days. Visit The Windows 8 Center at Sourceforge for all your go to resources. http://windows8center.sourceforge.net/ join-generation-app-and-make-money-coding-fast/ _______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel
