From: John Arbash Meinel <john@arbash-meinel.com>
To: Jason Earl <jearl@notengoamigos.org>
Cc: Christian Faulhammer <opfer@gentoo.org>,
bazaar@lists.canonical.com,
Daniel Clemente <dcl441-bugs@yahoo.com>,
emacs-devel@gnu.org
Subject: Re: Emacs Bazaar Repository II
Date: Wed, 22 Oct 2008 16:04:54 -0500 [thread overview]
Message-ID: <48FF9576.8040401@arbash-meinel.com> (raw)
In-Reply-To: <873aios6ap.fsf@notengoamigos.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Jason Earl wrote:
> Christian Faulhammer <opfer@gentoo.org> writes:
>
>> Hi,
>>
>> Daniel Clemente <dcl441-bugs@yahoo.com>:
>>
>>> The operation I use most is „log“: to see what's new, or if
>>> something was included or not, or when, or who did what when, etc. I
>>> have tested this second repository and also the first one. I used
>>> today's bzr (rev. 3788) and did several successive tests until the
>>> results stabilised.
>> Which bzr version are you using? 1.8 improved log performance
>> according to the release notes.
>>
>> V-Li
>
> I'm using bzr.dev and I get similar numbers for trunk on the emacs
> repository. Of course, this is on an underpowered laptop, but I still
> have a hard time waiting over a minute for log information.
>
> time bzr log > /dev/null
>
> real 2m7.347s
> user 1m52.223s
> sys 0m1.152s
>
> Even worse, just getting the last 10 revisions is also ridiculously
> slow.
>
> time bzr log -r -10.. > /dev/null
>
> real 1m5.250s
> user 0m59.520s
> sys 0m0.320s
>
> I didn't want to pile on with this particular complaint, as I know that
> it has been brought up before, but bzr log is really really slow on
> repositories with as many revisions as Emacs has.
>
> I really like bzr's log output, as it makes the branch merging very
> clear, but I really wish I knew of a sensible way to just get the last
> few changes on a branch.
>
> Jason Earl
>
>
Try "bzr log --short -r -10..-1 >/dev/null"
It should be surprisingly faster. I've been working with Vincent a
little bit to try and make our log layout and numbering not require
reading the whole ancestry.
Also, you might try using "--development2" format. At least if you want
to see an interesting comparison. Specifically, --development2 changes
the index format, which makes certain parts of "load-the-whole-ancestry"
perform a lot better. Obviously the best fix is to get rid of the
O(ancsetry) operation, but you can do some things to mitigate it in the
short term.
(With a recent bzr.dev or I believe bzr-1.8, you should be able to copy
your existing repository and just "bzr upgrade --development2")
If you are willing to do it, it would be interesting to see the result.
John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkj/lXYACgkQJdeBCYSNAAO4igCfYOT9nBA/2yQjWpII+7LN/Z8m
SZoAnjMlNZASBVBemVhbYOiwaxGouluQ
=5sYA
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2008-10-22 21:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-11 21:39 Emacs Bazaar Repository II Jason Earl
2008-10-19 23:56 ` Martin Pool
2008-10-21 22:07 ` Daniel Clemente
2008-10-22 18:46 ` Christian Faulhammer
2008-10-22 20:50 ` Jason Earl
2008-10-22 21:04 ` John Arbash Meinel [this message]
2008-10-22 21:40 ` Jason Earl
2008-10-22 22:16 ` Aaron Bentley
2008-10-26 17:33 ` Daniel Clemente
2008-10-26 19:37 ` Eli Zaretskii
2008-10-26 20:08 ` Mathias Megyei
2008-10-26 21:59 ` Robert Collins
2008-10-26 23:34 ` Andreas Schwab
2008-10-22 21:22 ` Daniel Clemente
2008-10-23 14:25 ` John Arbash Meinel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48FF9576.8040401@arbash-meinel.com \
--to=john@arbash-meinel.com \
--cc=bazaar@lists.canonical.com \
--cc=dcl441-bugs@yahoo.com \
--cc=emacs-devel@gnu.org \
--cc=jearl@notengoamigos.org \
--cc=opfer@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).