Performance improvements for bzr-2.4 on large trees

[Eli Zaretskii]

> Date: Thu, 26 May 2011 23:04:21 +0200
> From: John Arbash Meinel <john at arbash-meinel.com>
> CC: bazaar at lists.canonical.com
> 
> Basically, install the plugin like any other plugins. I think the
> Windows installer might have a special system plugins directory, but
> BZR_PLUGIN_PATH can be set, or you can use %APPDATA%/bazaar/2.0/plugins
> 
> Something like:
> 
>  bzr branch lp:bzr-history-db history_db

This part was already done.

> You then need to tell it that you want it to start caching branches that
> you care about. This can be set up globally, or just for specific
> branches, etc, etc. But you can do something like:
> 
>  bzr config history_db_path=C:/dev/historydb.db
> 
> You can use "bzr config --scope=???" to change where things get set. I
> don't know bzr config very well. I just edit bazaar.conf if I want it to
> apply to everything, and locations.conf if I want it to apply only in a
> directory.

I have a shared repo under which I have all the Emacs branches I care
about.  Can I use locations.conf to define a single history_db_path
for all of these branches, or do I need to modify branch.conf for each
such branch?  IOW, can locations.conf be used to make the DB affect
_less_ than a whole branch, or also to affect _more_ than just one
branch?

Also, is it a good idea to have a single DB for several branches in a
shared repo (assuming the branches share many revisions)?

Btw, the form of the argument to the --scope option of "bzr config" is
not really documented.  It says "Reduce the scope to the specified
configuration file", but that doesn't mean I need to specify a file
name there, does it?  I submitted a bug report about that
(https://bugs.launchpad.net/bzr/+bug/788991).

Thanks.