hg update on Windows
Michał Sznajder
michalsznajder at gmail.com
Fri Aug 23 05:37:58 UTC 2019
On Thu, Aug 22, 2019 at 5:17 PM Augie Fackler <raf at durin42.com> wrote:
> > On Aug 22, 2019, at 03:28, Michał Sznajder <michalsznajder at gmail.com> wrote:
> > I have a repo with ~120k files and 4 gb in .hg. I am using WIndows 10 and Mercurial 5.0. I have 8 core machine with SSD.
> >
> > When executing "hg update" I notice that hg.exe uses around 12% of CPU in Task Manager so one core is fully utilized. Stats look like that:
> >
> > λ hg --time update tip
> > 118496 files updated, 0 files merged, 0 files removed, 0 files unresolved
> > time: real 380.822 secs (user 149.062+0.000 sys 229.297+0.000)
> >
> > Is there a way to speed this up? I tried to use "--config worker.enabled=true" but I think it doesn't apply to this situation or does it?
>
> I think it would, except that we don't use workers much on Windows.
In what cases worker is actually used on other platforms? I had a look
on source code and I found that merge code uses worker. Are any other
areas using it?
>
> Did you exclude the directory in question from your antivirus? That typically makes an enormous difference.
>
I did disable AV. But to be sure I re-did my tests with AV enabled
and to my surprise there is no substantial difference (15-20 secs more
with AV enabled). Total CPU utilization is higher due to AV doing its
job but still in the range of 30%.
More information about the Mercurial
mailing list