interpreting --time output

[Arne Babenhauserheide]

To tell if data is telling the truth, why don't you compare the output of 

$ time hg status

with 

$ hg --time status 

And to check if system load is an issue, just do repeated tests, take the mean 
and calculate the standard deviation (means: do scientific measurements). 

That gives you a good overview on the real time needed, but it will take some 
time. 

Best wishes, 
Arne


Am Montag 13 Oktober 2008 07:17:24 schrieb TK Soh:
> I compared mainline's tip to 1.0.1 on Window XP, by running 'hg --time
> status' on the netbean repo:
>
> Hg 1.0.1:
> Time: real 16.408 secs (user 8.281+0.000 sys 6.891+0.000)
>
> mainline tip:
> Time: real 9.269 secs (user 5.078+0.000 sys 2.844+0.000)
>
> The 'real' time is obvious. But I wonder how I should interpret the
> user and sys time.
>
> Also, very often the time data varies from run to run due to varying
> system loading. So, it there anyway I can be sure if the data are
> 'telling the truth'?
> _______________________________________________
> Mercurial mailing list
> Mercurial at selenic.com
> http://selenic.com/mailman/listinfo/mercurial

-- 
-- My stuff: http://draketo.de - stories, songs, poems, programs and stuff :)
-- Infinite Hands: http://infinite-hands.draketo.de - singing a part of the 
history of free software.
-- Ein Würfel System: http://1w6.org - einfach saubere (Rollenspiel-) Regeln.

-- PGP/GnuPG: http://draketo.de/inhalt/ich/pubkey.txt
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
Url : http://selenic.com/pipermail/mercurial/attachments/20081013/76082872/attachment.pgp