comparison CHANGELOG @ 5778:84affb254cdf

evolvecmd: don't update working copy when using in-memory merge This patch removes the update of the working copy after each in-memory merge and only instead updates the working copy afterwards (if requested). There's still no significant speedup in the hg repo. It seems that the cost of updating the working copy is not large enough to make much difference, and the cost of reading and updating obsmarkers is relatively high in that repo. A significant part of the time (~35%) is spent in `repoview.computehidden()` because it is recalculated for every commit (seems like potential for improvement). I made similar changes in the mozilla-unified repo (which has a significantly larger working copy), by adding 10 commits each changing one line of a file. There, evolving 9 of those commits took 34s before this patch and 20s after. I measured similar speedups in an internal repo (9.0s -> 5.2s).
author Martin von Zweigbergk <martinvonz@google.com>
date Tue, 24 Nov 2020 16:33:24 -0800
parents eadc1d09f2f5
children d0389ddf402d aad3ee70a0bb
comparison
equal deleted inserted replaced
5777:c5dfbbe4363d 5778:84affb254cdf