On Sun, Jul 31, 2011 at 14:03, Derek Gaston <[email protected]> wrote:
> Sweet! Any timing numbers on this? We see a pretty good chunk of our
> runtime getting eaten up by mapping...
>
This patch does not change the algorithm at all, it just uses a public API
to access the local-to-global mapping (which we have moved around, so the
private access will not work anymore).
The right solution here is to get rid of the global-to-local mapping. There
is no algorithmic reason to need it (at least in performance-sensitive
locations). The local-to-global mapping is fast and scalable, so it should
not be an issue.
------------------------------------------------------------------------------
Got Input? Slashdot Needs You.
Take our quick survey online. Come on, we don't ask for help often.
Plus, you'll get a chance to win $100 to spend on ThinkGeek.
http://p.sf.net/sfu/slashdot-survey
_______________________________________________
Libmesh-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/libmesh-devel
