[Mono-dev] Logging profiler timings are way off

[Massimiliano Mantione]

Sorry for the *late* reply... I've had problems with my mailbox
lately :-(

On Sat, 2009-01-17 at 17:11 +0100, Paul Melis wrote:
> While looking at the GC statistics after a profiler run which used
> --profile=logging:c I noticed the following times that seem to be the
> result of overflow/uninitialized vars:
> [...]
> What's a good way to move forward on this?

You should try to use the "force-accurate-timer" profiler option as
documented on the "mono(1)" man page.

What happens is likely that rtdsc ends up being non-monotonic, but since
the timer values are handled as unsigned quantities if they underflow
they become huge numbers.

I'm still pondering if using the accurate (and slower) timer should be
the default instead...

Thanks,
  Massi