Hello all, I've been trying to do some profiling of some of the libMesh examples and am having some issues understanding the generated gprof output. It seems like much of the data that I am expecting is missing from the output (please see attached logs). I compile with METHOD=prof (with the minor hiccup mentioned in issue #1776) and the example builds as expected with the -pg flags appearing in both the compilation and linker lines of the example as well as the config.log summary during the library build.
For the example gprof logs attached, I ran a vanilla intro/ex3 where the only change consisted of an increase in the number of elements to allow for a nontrivial runtime. Basically the only thing that gprof seems to report is all the time being spent in assemble and exact_solution, with very little mention other things which are clearly visible in the libMesh perflog. Has anyone run into similar issues or have any clues as to what I can try to produce more granular output? Thanks for any info you can provide! - Boris ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Libmesh-users mailing list Libmesh-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-users
