copy shamap as well when cloning/pulling
Bug #486570 reported by
Russel Winder
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Bazaar |
Invalid
|
Wishlist
|
Unassigned | ||
| Bazaar Git Plugin |
Triaged
|
Low
|
Unassigned | ||
Bug Description
Turning an email on the mailing list into a bug report as requested:
My original email:
"Updating the git map, as happens after taking a branch of a Bazaar
branch bound to a Git repository which is then bound to the same Git
repository and updated, takes ages. We cannot blame NFS and TDB here as
this is on the machine with the real discs locally. It has taken about
45mins to update the git map for 1749 revisions.
It gets worse :-( it then fetched 38 revisions and this took about 50
mins."
Jelmer responded:
"Please file a bug about this. We should probably get bzr to provide a
hook that can be used to copy the sha map when cloning a bzr branch."
Clearly further experiments are needed to get proper problem data . . .
Revision history for this message
| Jelmer Vernooij (jelmer) wrote | #1 |
| Changed in bzr-git: | |
| status: | New → Triaged |
| importance: | Undecided → Wishlist |
| importance: | Wishlist → Low |
| Changed in bzr: | |
| status: | New → Triaged |
| importance: | Undecided → Wishlist |
| status: | Triaged → Confirmed |
| summary: |
- updating the git map and pulling revisions takes a very long time + copy shamap as well when cloning/pulling |
| tags: | added: foreign hooks hpss |
Revision history for this message
| Jelmer Vernooij (jelmer) wrote | #2 |
| Changed in bzr: | |
| status: | Confirmed → Invalid |
To post a comment you must log in.
This requires bzrlib to provide a hook on repository clones/pulls first.