On Mon, Jul 7, 2008 at 3:01 PM, Esther Verreau
< everreau%40ccl.northwestern.edu">everreau
ccl.northwestern.edu> wrote:
> Yes, you should take a look at the profiler extension, it's included in
> the 4.0.2 download.
thanks esther; i must be blind... "RTFM" would have been a perfectly
appropriate response here!
anyway, i played around with the profiler and found it to be
slow and not entirely reliable (i was getting 117 years
as the time taken for one procedure!).
blissfully the source code is all there, so i had enough info to rewrite
it a bit more efficiently, taking the overhead from 440% to 36%, still
more than i'd prefer, but a lot better than the old one.
in case someone might find it useful, i've attached a copy of
the new code. just drop it into the extensions/profiler/src directory, rebuild,
and use:
profiler:set-class "org.nlogo.extensions.profiler.QuickTracer"
to use it (in exactly the same way as the original).
i wonder, is there any way to map from an Activation's return address
to its position in the source code? that way it might be possible to get a bit
more detail out of the profiling without incurring much more
overhead.
thanks for all your ever helpful replies,
rog.
.