On Thu, 31 Jul 2008, Shengli Xu wrote: > Roy, Could you tell me what specific profiling information should be > gotten? I have to solve this problem.
Just this: "Exactly where is the delay occurring?" If you're using our PerfLog objects, for example, you could create one in the assembly, activate it right before the matrix adds, and deactivate it right after; if that ends up being responsible for most of your runtime then you've verified that my "bad matrix assembly" hypothesis was correct. If not, then something else in your assembly is taking way too long (calling FE::reinit inside the quadrature loop?); you can use fine-grained PerfLog objects to test that out too. Or use whatever profiler you're comfortable with, of course. I like oprofile; other people I know prefer Tau. http://oprofile.sourceforge.net/ http://www.cs.uoregon.edu/research/tau/home.php --- Roy ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
