I have a program, compiled with cost-center profiling on, that takes about 5
minutes, 30 seconds to run (measured with a stopwatch), but the resulting .prof
file reports the total time as 34 seconds. I know that this number doesn't
include overhead due to profiling, but surely the overhead can't
I have a program, compiled with cost-center profiling on,
that takes about 5
minutes, 30 seconds to run (measured with a stopwatch), but
the resulting .prof
file reports the total time as 34 seconds. I know that this
number doesn't
include overhead due to profiling, but surely the
On Tue, Oct 21, 2003 at 05:21:37PM +0100, Simon Marlow wrote:
I think the profiler only measures CPU time, so if the program is
waiting for I/O or sleeping a lot of the time, that won't be included in
the profile.
I don't think that's the issue -- when I run the program with debugging flags
I think I understand what's going on: GC time isn't counted as part of
the time reported by profiling. This seems misleading to me, since if your
program is spending 4 times as much time doing GC as doing actual work
(such as mine is), you'd want to know about it... but I suppose you can
always
[Sorry if this shows up twice -- I accidentally posted from the wrong address
and left something out.]
I have a program, compiled with cost-center profiling on, that takes about 5
minutes, 30 seconds to run (measured with a stopwatch), but the resulting .prof
file reports the total time as 34
