Re: issue 2043 profiling data

> >There is one problem though: The program ran for about 4 hours, but the
> >gprof table seems to suggest that only 328.51 seconds elapsed in
> >look_up_committable (which is 93% of all time elapsed).
> >
> >Can someone help me explain the data above and the relation with the
> 'time'
> >output which gives 229minutes?
> >
> >
> I think gprof will show CPU time, while most of the wall clock time is
> blocking in I/O. 'time' should actually tell you user, system and wall
> clock time; which of them is 229 minutes?

From another run I got this:

real 238m51.263s
user 226m19.327s
sys 2m3.196s

So real and user are not that far apart. Do you mean that real is wall-clock
and user is processor time? Tobias was trying to convince me the problem was
with swapping and waiting for the I/O, but if you are correct, then swapping
will not be the cause of this long execution time.

bye,

Erik.

-- 
NEU: Bis zu 10 GB Speicher für e-mails & Dateien!
1 GB bereits bei GMX FreeMail http://www.gmx.net/de/go/mail
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org