Simon Marlow wrote:
That's right - the general idea is to make the profile insensitive to other loading on the machine. I can see there might be an argument for making this tweakable, though.
This would be nice to have if one is trying to correlate behavior with specific I/O events in time (i.e. messages coming into a server).
Alloc Collect Live GC GC TOT TOT Page Flts bytes bytes bytes user elap user elap 264424 262144 20592 0.00 0.00 0.03 0.01 0 0 (Gen: 1) 311540 270336 63732 0.00 0.00 3.84 5.25 0 0 (Gen: 0)
So between these first two GCs, your program spent nearly 4 seconds doing something, but only allocated 300k. What was it doing? If I'm not mistaken, it's negotiating a TLS session.
I think I tracked down the bizarre timetag issue, it is already in Trac: http://hackage.haskell.org/trac/ghc/ticket/769 So the out of order timetag of 3.100 in my original e-mail should really be 4.0. Rich