Re: which time is counted by TStopwatch or what is CINT actually

Valery Fine (fine@rsgi01.rhic.bnl.gov)
Mon, 19 Jan 1998 20:01:41 +0100


On 20 Jan 98 at 0:23, Pasha Murat wrote:

>
>
> Hello,
>
> in the example below I'm interactively running 2 test routines which
> I consider to be exactly the same from the point of view of
> execution: the only difference between them consists in that one
> line which
> *should never be executed* is uncommented in the second routine.
>
> I'd also expect the execution times to be exactly the same.
> However ROOT TStopwatch timer reports *very* strange results:
> the reported times differ by more than a factor of 100...
>
> One could either suspect TStopwatch timer in reporting wrong time in
> one of 2 cases or CINT in doing much more than it has been asked to
> in case when `cout ...' is uncommented.
>

I did try this under Windows and got:

root [0] .x pasha1.C
RealTime=36.452000 seconds, CpuTime=35.641250 seconds
NULL
root [1] .x pasha2.C
RealTime=0.170000 seconds, CpuTime=0.170245 seconds
NULL
root [2]

But I saw no evidence aganist of TStopwatch since a normal
watch just provided the same time: 36 sec vs 0.17

So I suspect it is CINT problem not TStopwatch.

Valery
=================================================================
Dr. Valeri Faine (Fine)
------------------- Phone: +1 516 344 7806
Brookhaven National Laboratory FAX : +1 516 344 4206
Bldg. 510A /STAR mailto:fine@rsgi01.rhic.bnl.gov
Upton, New York, 11973-5000 http://nicewww.cern.ch/~fine
USA

Dr. Valery Fine Telex : 911621 dubna su
-----------
LCTA/Joint Inst.for Nuclear Res. Phone : +7 09621 6 40 80
141980 Dubna, Moscow region Fax : +7 09621 6 51 45
Russia mailto:fine@main1.jinr.dubna.su