Speedup with history-db
John Arbash Meinel
john at arbash-meinel.com
Tue Jun 7 12:35:23 UTC 2011
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 6/4/2011 9:54 AM, Eli Zaretskii wrote:
>> Date: Tue, 31 May 2011 20:27:01 +0300
>> From: Eli Zaretskii <eliz at gnu.org>
>> Cc: bazaar at lists.canonical.com
>>
>>> Date: Tue, 31 May 2011 16:25:31 +0200
>>> From: John Arbash Meinel <john at arbash-meinel.com>
>>> CC: bazaar at lists.canonical.com
>>>
>>>> Fair enough. The only use cases that really bothers me is this
>>>>
>>>> bzr log --include-merges -c REVISION
>>>>
>>>> This is something I do quite a lot, because I like to know what went
>>>> into merge commits and people tend to not describe that adequately in
>>>> the log message of the merge. This command does not mention dotted
>>>> revnos, only revisions on the mainline (I do understand that -
>>>> --include-merges is a reference to dotted revnos in disguise). The
>>>> output of the above command must be accurate, otherwise I will be
>>>> forced to use --no-plugins, because I cannot trust the output. It
>>>> would be nice if it could be fast as well, but accuracy is more
>>>> important.
>>>>
>>>> Thanks.
>>>
>>> That still works. The example that fails is:
>>>
>>> bzr log -rDO.TT.ED..X
>>>
>>> - -c X will always use 2 mainline revisions.
>>
>> Not with the specific revision I somehow managed to find:
>>
>> bzr log --include-merges -c104363
>>
>> Several other merge-commits I tried indeed work (and are about 15
>> times faster with the plugin than without it). But this single
>> revision 104363 causes trouble. Could you please take a look at the
>> above command with that specific revision on the Emacs trunk?
>
> Same thing happens with revision 104482, committed today to the Emacs
> trunk. Since the output is relatively short, I will show it here
> (below). You can see as the output with the plugin shows much more
> revisions than expected.
>
> Could you please take a look at these two instances? Other than that,
> the plugin seems to work just great, and slashes the times for "bzr
> log" and "bzr status" by very large factors.
>
> Here's the output with and without the plugin:
>
One thing you could try, is "bzr log -Dhistory_db". It puts a little bit
of extra info to stdout. I don't know if it will be enough or not, but
it might help. (It might at least indicate if we are picking a random
revision, etc.)
John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk3uGwsACgkQJdeBCYSNAAOPGwCgwzDwI2lo0CR7/aEOv2M0czfG
YBkAn1N7AOkvxgMHojgks6jjPOhky/qN
=1caM
-----END PGP SIGNATURE-----
More information about the bazaar
mailing list