Profile of hg clone on windows

Matt Mackall mpm at selenic.com
Mon Sep 19 15:19:07 CDT 2005


On Mon, Sep 19, 2005 at 01:05:43PM -0700, Matt Mackall wrote:
> > $ time find upstream | wc
> >   32410   40794 2542038
> > 
> > real    0m12.654s
> > user    0m2.061s
> > sys     0m10.826s

Ok, sys here is a bit weird. It seems to be including I/O wait time or
something.

> > (now in windows' cmd)
> > C:\src>hg --time clone upstream clonetimetest
> > Time: real 81.354 secs (user 11.266+0.000 sys 4.875+0.000)
> 
> So we took 16 seconds to do all the crunching (user+sys), and spent
> the rest of the time waiting.
> 
> > C:\src>hg --time clone -U upstream clonetimetest3
> > Time: real 21.500 secs (user 4.641+0.000 sys 0.875+0.000)
> 
> And here we took 5.5 seconds seconds of CPU time.
> 
> Either your filesystem or disk is slow, or there's significant other load on
> your machine.

Btw, if your machine is otherwise unloaded, this really points to bad
caching or journalling behavior in NTFS. You should sanity check the
above numbers again the performance monitor graph app thingy.

-- 
Mathematics is the supreme nostalgia of our time.


More information about the Mercurial mailing list