revision texts do not seem to be properly combined into groups
Bug #402656 reported by
John A Meinel
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Bazaar |
Confirmed
|
High
|
Unassigned | ||
| Breezy |
Triaged
|
Medium
|
Unassigned | ||
Bug Description
As part of investigating bug #402114
It would appear that the revision texts are not properly combined into large groups. If you read the debug log it would appear that we are reading approx 500 bytes many many times.
This is not universal, as there are a few very large fetches, but they are surrounded by fairly small fetches *from the same pack file*. (see the time around 120s into the log.)
This could just be a symptom of: bug #402645 and/or bug #402652
Specifically, if the source had one well optimized pack, and a bunch of 'loose' packs, then it is likely that fetching from that source would generate a single semi-optimized pack.
We might just close this as a dupe if it turns out to be exactly the same root cause.
Revision history for this message
| Robert Collins (lifeless) wrote | #1 |
| Changed in bzr: | |
| importance: | Medium → High |
| Changed in bzr: | |
| status: | Triaged → Confirmed |
| tags: | added: check-for-breezy |
| tags: |
added: performance removed: check-for-breezy |
| Changed in brz: | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
To post a comment you must log in.
it does look like 402652 would be driving this.