Performance improvements for bzr-2.4 on large trees

[John Arbash Meinel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


...
>> 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?

I don't know what you mean by "less than a whole branch". In
locations.conf if you set a policy like:

[C:/path/to/my/repo]
history_db_path = C:/path/to/my/repo/history.db

Then all branches at  C:/path/to/my/repo/branch, etc will use the same
historydb file.

I'm pretty sure the answer is "yes", but I'm a bit confused by the question.

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

I certainly recommend sharing history_db for any branch that shares
history. Updating just the newest revisions for a branch usually takes
on the order of 100ms or so, while importing the whole history takes
15-30s. Not to mention the size of the history.db file itself.

> 
> 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.

Yeah. I think --scope is probably a RegistryOption, but we have a bug in
our help tools when you have a RegistryOption that doesn't expand its
flags. (See 'bzr help merge' which has "--merge-type=ARG" allowing you
to say "--merge-type=weave", but also expands them as "--weave", and
they get documented under the latter name.)

https://bugs.launchpad.net/bzr/+bug/730905

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk3fWRwACgkQJdeBCYSNAAP9SwCglK5da22VPHBeQhBPPjvIkmAL
hBgAnjgyMraePGPmhUE3qVYH/B+goXKU
=Itu5
-----END PGP SIGNATURE-----