bzr explorer is almost unusable with medium-big tree (e.g. bzr.dev size)
Bug #582838 reported by
Alexander Belchenko
This bug affects 10 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar Explorer |
Confirmed
|
High
|
Unassigned | ||
QBzr |
Confirmed
|
Medium
|
Unassigned |
Bug Description
I'm dogfooding explorer with bzr.dev. My first impression that explorer unusable on such big trees. I have to disable automatic refresh to get it more responsive. But if I'll start to play with working tree filters and change it between different states quickly, then explorer becomes frozen for several minutes and get ~100% load on one core.
We need better asynchronous execution of refresh/change operations both in explorer and qbzr.
tags: | added: feel-faster multiprocess performance |
Changed in qbzr: | |
importance: | High → Medium |
To post a comment you must log in.
Gary, do you have any ideas why changing filter of treebrowser has such frozen effect?