https://bz.mercurial-scm.org/show_bug.cgi?id=6036
Bug ID: 6036 Summary: `hg update` can take too much of memory on large repos Product: Mercurial Version: default branch Hardware: PC OS: Linux Status: UNCONFIRMED Severity: feature Priority: wish Component: Mercurial Assignee: bugzi...@mercurial-scm.org Reporter: 7895pul...@gmail.com CC: mercurial-devel@mercurial-scm.org There have been good amount of instances internally that `hg update` takes a lot of memory and aborts saying "abort: Cannot allocate memory". Following are things which I have noticed: 1) updating from tip to 0 revision or vice versa can take upto 1 GB of memory on Mozilla repo 2) Internally updating from 0 to tip is taking 7-8 GB of memory. There are internal reports about `hg update` taking 20GB's of memory too. I agree we have a large repo but update should still work better. We generally update from rev 0 to tip after clone and that's where we are hitting this problem mostly. -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel