On Monday 22 October 2007, Hamish wrote: > Hi, > > > I have run valgrind's callgrind profiler for v.what.rast. > > results + screen dumps are here: > http://bambi.otago.ac.nz/hamish/grass/dev/ > > > to look at it in detail install kcachegrind and graphviz, then just > kcachegrind <file> > > (after un-gzipping the callgrind output files) > > > I added what I did as an example on the wiki debugging page: > http://grass.gdf-hannover.de/wiki/GRASS_Debugging#Kcachegrind >
Very cool. It would be neat to apply this to more GRASS functions to see what is eating CPU time. Cheers, Dylan > > quick summary of results: > 99.5% of the cost was taken by the dbf process, not v.what.rast > (watching 'top' shows you the same) > > In the dbf process (#15561) about 1/3rd was taken by G_debug(), > and about 1/2 was taken by G_debug() + G_strcasecmp() > > > Hamish > > > __________________________________________________ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam protection around > http://mail.yahoo.com > > _______________________________________________ > grass-dev mailing list > grass-dev@grass.itc.it > http://grass.itc.it/mailman/listinfo/grass-dev -- Dylan Beaudette Soil Resource Laboratory http://casoilresource.lawr.ucdavis.edu/ University of California at Davis 530.754.7341 _______________________________________________ grass-dev mailing list grass-dev@grass.itc.it http://grass.itc.it/mailman/listinfo/grass-dev