cache: avoid warming the fnodetags cache after clone
That cache can quite expensive to compute on large repository as not that `hg clone` is warming all cache, this can introduces a significant slowdown for clone time[1]. As a stop gap measure introduce a quick fix for that on stable, skipping the fnodetags cache post-clone. [1] https://www.mercurial-scm.org/pipermail/mercurial/2021-April/052679.html Differential Revision: https://phab.mercurial-scm.org/D10695
Showing
- mercurial/hg.py 1 addition, 1 deletionmercurial/hg.py
- mercurial/localrepo.py 8 additions, 2 deletionsmercurial/localrepo.py
- tests/test-clone-uncompressed.t 0 additions, 1 deletiontests/test-clone-uncompressed.t
- tests/test-clone.t 0 additions, 2 deletionstests/test-clone.t
- tests/test-hardlinks.t 0 additions, 2 deletionstests/test-hardlinks.t
- tests/test-share.t 0 additions, 1 deletiontests/test-share.t
- tests/test-ssh.t 1 addition, 1 deletiontests/test-ssh.t
- tests/test-tags.t 10 additions, 10 deletionstests/test-tags.t
- tests/test-treemanifest.t 2 additions, 2 deletionstests/test-treemanifest.t
Loading
Please register or sign in to comment