"Check Action Availability" is file system intensive...

[Andir]

If you work with files on a network share, this option seems to bring right click menus and Eclipse to a crawl.

Could (Shouldn't) this information be cached locally? I realize there may be a conflict if someone updates a file between caches, but it "feels" like it may be polling every file for a change instead of the currently selected one? I don't know how to go about improving performance of this aspect, but it seems to me like there would be a better way than freezing eclipse for the 1-2 minutes it takes to poll the remote bzr repository for status every time you right click on a file to perform some non-bazaar action.

In this instance, I cannot work locally. It's for web development in a team environment. Files must be on remote share. (We tried file-sync to work local and upload our files automatically... but it's only a one way sync that overwrites other people's changes.)

[Guillermo Gonzalez (verterok)]

Hi,

Thanks for reporting this issue.

Yes, the check of an action is basically a bzr call on that file, so it's expensive if you'r using bzr in a network share.

There is an option to disable the check of action availability, but besides that the idea behind bzr is that branching and merging is cheap and easy, so I'ld recommend disbaling the "check action availability" or change the workflow to one of the recommended in the bzr documentation: http://doc.bazaar.canonical.com/latest/en/user-guide/bazaar_workflows.html

Regards,

[Alexander Taler (alex-idereal)]

Piotr committed several improvements to status caching, so we expect that to address your concerns