TortoiseBZR behaves very slow on big working tree.

[tinyfish]

I have a working tree of 15.3 GB, 404,657 files and 4,591 folders. The .bzr folder is 6.18 GB, with only 1 revision.
TortoiseBZR behaves very slow on that repository:
 * tbzrcache.exe takes minutes to generate cache, with CPU usage over 50%. I've seen #330761 recommends the "shell" option, which solved the same problem in TortoiseSVN.
 * Commit takes 30s to initialize the dialog. Since commit dialog check the whole working tree for status, I need only the status of current directory. Other commands such as add, revert, Bazaar Explorer...have the same problem.
 * "Browse Inventory" spend much time to initialize, and more time to expand a directory.

[methane (songofacandy)]

>I've seen #330761 recommends the "shell" option, which solved the same problem in TortoiseSVN.

'shell' option is not good on bzr because:

 * bzr stores control files on top directory instead of every directory like svn.
 * Running Python as shell extension is dangerous. Shell extension is loaded many apps and
    Python may conflicts other Python program.

So, more non-volatile cache is better option. (sqlite?)

> * Commit takes 30s to initialize the dialog. Since commit dialog check the whole working tree for status, I need only the status of current directory. Other commands such as add, revert, Bazaar Explorer...have the same problem.

Can "bzr view" ease your pain?

[tinyfish (rgvuce)]

Thanks for reply.

Maybe 'shell' option like TortoiseSVN is not suitable for TortoiseBZR. Non-volatile cache can solve the problem, and SHChangeNotifyRegister() may improve performance.

I tried bzr view but it tell me dirstate is locked by tbzrcache.exe.

In fact, I want to use TortoiseBZR in a team, instead of TortoiseSVN. They need a GUI tool work smoothly like TortoiseSVN. TortoiseBZR is a good solution. I prefer any way can solve these problems quickly.