[GRASS-dev] v.what.rast speedup
dylan.beaudette at gmail.com
Tue Oct 23 13:23:54 EDT 2007
On Monday 22 October 2007, Hamish wrote:
> I have run valgrind's callgrind profiler for v.what.rast.
> results + screen dumps are here:
> 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:
Very cool. It would be neat to apply this to more GRASS functions to see what
is eating CPU time.
> 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()
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam protection around
> grass-dev mailing list
> grass-dev at grass.itc.it
Soil Resource Laboratory
University of California at Davis
More information about the grass-dev