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
Rich Fought wrote:
IIRC the timestamps ignore time spent in GC and time spent sampling
the heap, so they measure runtime of the program only.
So if I have a server that is idle most of the time waiting for
requests, the timestamps recorded in the heap profile will not be "real
time" but pr
On a separate issue, I can't seem to get the -hcname or -hmname options
to work. For instance, profiling with just -hm yields an entry for
module Network.HTTP, yet when I try to profile again with
-hmNetwork.HTTP, I do not get a heap dump. Is there some special
formatting I am missing?
Than
Simon Marlow wrote:
IIRC the timestamps ignore time spent in GC and time spent sampling
the heap, so they measure runtime of the program only.
So if I have a server that is idle most of the time waiting for
requests, the timestamps recorded in the heap profile will not be "real
time" but prog
Rich Fought wrote:
I'm trying to use heap profiling with +RTS -hc -i1 options and running
my program for about 30 seconds. However, I only get around 7 samples
with seemingly bogus timetags (i.e. 0.00, 3.69, 3.73, 3.10, 4.05,
4.12). What's going on?
I'm running GHC 6.4.2 on Windows (MSYS/Mi
I'm trying to use heap profiling with +RTS -hc -i1 options and running
my program for about 30 seconds. However, I only get around 7 samples
with seemingly bogus timetags (i.e. 0.00, 3.69, 3.73, 3.10, 4.05,
4.12). What's going on?
I'm running GHC 6.4.2 on Windows (MSYS/MinGW).
Thanks,
Rich
