From: Pavel Vozenilek (pavel_vozenilek_at_[hidden])
Date: 2005-02-04 20:31:27
"christopher diggins" wrote:
>> - ability to report data only when certain threshold is reached
> Threshold of what?
I mean no data are reported unless the time is more then
given value. Like:
MEASURE_TIME("xyz", 10 /* millis */)
>> - collecting min/max/average statistics where needed
> This could be done relatively easily, I believe by writing a new policy.
> Would you be interested in writing a statistics collecting policy?
> One thing that concerns me is that as far as statistics go, this will
> likely have far too coarsely grained resolution to be used, as one would a
> real profiler. Due to the resolution of the underlying boost::timer. This
> is instead useful only for large and extremely CPU intensive blocks of
I use high-resolution timers for Win32.
It is even possible to go down and count clock
via CPU register. This can be done in profiler as well.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk