Speed up the mercurial plugin for large repositories #4399
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In very large repositories, certain hg commands can take a very long time. Two of those used in the mercurial plugin are particularly bad -
hg status
andhg summary
. I removed thehg summary
call by replacing it withhg root
, which gives us similar information much faster.hg status
was a different beast, and since there is no "faster" replacement I ended up just mirroring the functionality of the git plugin. If you're unfamiliar, the git plugin simply shows the clean prompt if a certain config flag is set (oh-my-zsh.hide-dirty
). This approach has multiple benefits, the most important being that you can configure it per-repository.Finally, the multiple
in_hg
calls ended up callinghg root
a lot. These were not super long calls on their own, but when we do it often we end up spending quite a bit of time calculating an answer we already know. To fix this I saved it in a local variable at the beginning of thehg_prompt_info
call and remove it at the end.