5 Feb
2005
5 Feb
'05
8:44 a.m.
christopher diggins wrote:
- 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 code.
I have a boost::timer interface compatible high resolution timer here, which I can submit, if anybody is interested. Regards Hartmut