no indication why heavyweight checkout is slow
Bug #538868 reported by
Martin Pool
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Bazaar |
Fix Released
|
Medium
|
Parth Malwankar | ||
Bug Description
lithe% bzr checkout ~/bzr/trunk ~/tmp/t1
bzr checkout ~/bzr/trunk t1 437.82s user 6.38s system 93% cpu 7:54.26 total
This seems very slow for just copying all the history locally, but also this is something the user might expect to be fast.
We should show a message that all the history is being copied to a new directory at ~/tmp/t1 so they at least have a clue what is happening. This would be useful whether or not we make checkouts light by default.
Related branches
lp:~parthm/bzr/538868-message-for-heavy-checkout
- Vincent Ladeuil: Approve
- Gary van der Merwe: Abstain
- John A Meinel: Needs Fixing
- bzr-core: Pending (2nd review) requested
- Martin Pool: Pending (2nd review) requested
-
Diff: 357 lines (+160/-23)8 files modifiedNEWS (+3/-3)
bzrlib/builtins.py (+0/-5)
bzrlib/recordcounter.py (+86/-0)
bzrlib/remote.py (+2/-1)
bzrlib/repofmt/groupcompress_repo.py (+23/-4)
bzrlib/repository.py (+6/-4)
bzrlib/smart/repository.py (+40/-4)
bzrlib/tests/blackbox/test_checkout.py (+0/-2)
| Changed in bzr: | |
| status: | Confirmed → In Progress |
| assignee: | nobody → Parth Malwankar (parthm) |
| Changed in bzr: | |
| status: | In Progress → Fix Released |
| milestone: | none → 2.2b3 |
To post a comment you must log in.
