-
Notifications
You must be signed in to change notification settings - Fork 423
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mercurial "outgoing" check is slow #217
Comments
You could also use the |
I encounter some slowness with Mercurial repositories too. I think it is due to The fact is, git and Mercurial works quite differently on the remote handling aspect. The remote tracking system of git allow you to handle a kind of image of remote branches, but in local. But this means it is only based on the fetched informations from remotes. On the other side, Mercurial won't know nor maintain any information from the remote, unless ``hg outgoing`is called, and if the default remote is indeed on a remote server (either accessed through http or ssh), there will be a perceptible lag. I tend to focus on the state of the current working directory, not the diff with the remote, so I suggest adding an option to disable remote checking on mercurial at least. |
If it is slow because it does contact the remote server, I think we should completely remove the "hg outgoing" feature, instead of just allow to disable it. @anthonygelibert I've seen you had disabled "hg outgoing" in your repo. What do you think? |
I noticed your discussion on the subject and I didn’t answered because, in my opinion, my solution is just an hack. My problem was the same than everyone, the outgoing call is “very” expensive especially when you have bad Internet connection. It’s only to transform the call to outgoing into : So, like it’s very cheap I didn’t mentioned it. |
@anthonygelibert Do you sometimes feel the need of enabling your LP_ENABLE_HG_OUTGOING, or do instead leave it always to off in practice? |
I didn’t choose to disable it for nothing ;-). I never never enable it, honestly. I prefer to call it from command line when required. |
This seems like a similar question to #19 but for Mercurial.
Setting "LP_ENABLE_HG=0" fixes the problem. The repo that this is happening on is approximately 700MB. Curious if anyone had any performance tips around this issue.
The text was updated successfully, but these errors were encountered: