bzr log . in a subdir is slow
Bug #721250 reported by
Per Johansson
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Confirmed
|
High
|
Unassigned | ||
Breezy |
Triaged
|
Medium
|
Unassigned |
Bug Description
bzr log . in a subdirectory in our source tree is really slow.
: [dev ~/src/sub/dir]; time ~/bazaar/
real 118m29.958s
user 116m10.968s
sys 2m14.741s
That's just under 2 hours, my colleagues are complaining, which is understandable...
The machine was otherwise mostly idle during this.
The repository is about 400M and has 21670 revisions, 2a format.
The attached callgrind is for bzr 2.3.0 source release, using CentOS 5 and python 2.4
Related branches
description: | updated |
Changed in bzr: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
importance: | Medium → High |
tags: | added: log performance |
tags: | added: check-for-breezy |
Changed in brz: | |
status: | New → Triaged |
importance: | Undecided → Medium |
tags: | removed: check-for-breezy |
To post a comment you must log in.
Are you using the compiled extensions ?
The python code ensures compatibility where the extensions *can't* be compiled but there is a significant performance penalty there.
There should be warning about it if that's the case.