-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Improve performance of the Bazaar VCS backend #5445
Conversation
the failing build was a travis issue, i restarted the offending element |
Looks like the same as git's --depth parameter and related discussion. |
A distinction between git's --depth parameter and bzr's lightweight checkouts is that history in bzr's case is not truncated; any access of history (which should be rare) will result in bzr contacting the remote repository to retrieve the missing history (lazily). |
@pradyunsg basically gits '--depth' is a half-assed feature that breaks half the world, while bzr pretty much did light checkouts correctly |
@jelmer Could you link to the issues that this PR should close (using the GitHub auto close 'magic')? (on mobile) |
Done. |
FYI - linter check is failing. |
Sorry, fixed now. |
Hello! I am an automated bot and I have noticed that this pull request is not currently able to be merged. If you are able to either merge the |
Done. |
Hello! I am an automated bot and I have noticed that this pull request is not currently able to be merged. If you are able to either merge the |
Thanks, cjerdonek. Is there anything I can do to help get this merged? upstream keeps changing under me. |
Hello! I am an automated bot and I have noticed that this pull request is not currently able to be merged. If you are able to either merge the |
ping, any news on this? |
Thanks @jelmer for being so patient! @cjerdonek could you please take a look at this? |
ping @cjerdonek |
Here are some high-level comments on this PR. My apologies for not taking a look sooner, but I've never used Bazaar, so I felt like I might not be qualified to review the PR. My comments below are merely high-level.
|
As discussed earlier in this pull request, lightweight checkouts in bzr are different from shallow checkouts in Git and the considerations for dropping git shallow clones don't apply here: A distinction between git's --depth parameter and bzr's lightweight checkouts is that history in bzr's case is not truncated; any access of history (which should be rare) will result in bzr contacting the remote repository to retrieve the missing history (lazily). I'll see if I can split up this pull request into two separate ones. |
I've split the export part out into a separate proposal: #6139 |
Hello! I am an automated bot and I have noticed that this pull request is not currently able to be merged. If you are able to either merge the |
Closing this since it's bitrotten. Please file a new PR if there's still interest in this. |
Improve performance of the Bazaar VCS backend:
This significantly improves performance for Bazaar branches. E.g. for installing bzr itself ("bzr+lp:bzr"):
Performance on my system for 'bzr co --lightweight lp:bzr':
Performance on my system for 'bzr branch lp:bzr' (current behaviour):
Fixes #5443
Fixes #5444