Comment 8 for bug 849087

Revision history for this message
Gordon Tyler (doxxx) wrote :

I've also noticed that updates (i.e. 'bzr up') are taking quite a while now and there's a LOT of disk activity, disproportional to the actual amount of change. Most of the time seems to be spent reading the revisions between the one that's on my disk and the most recent revision on the server. It takes a few seconds to read each revision and it seems to be reading every revision in that range regardless of which part of the repo each revision affects, even revisions which don't affect what I have checked out.

Can I do something to reset the sqlite cache maybe?