unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Daniel Clemente <dcl441-bugs@yahoo.com>
To: bazaar@lists.canonical.com
Cc: emacs-devel@gnu.org
Subject: Re: Emacs Bazaar Repository II
Date: Wed, 22 Oct 2008 00:07:18 +0200	[thread overview]
Message-ID: <87d4htd2ll.fsf@yahoo.com> (raw)
In-Reply-To: e01316480810191656m30cacd6cg6acfbc913df21ce3@mail.gmail.com

"Martin Pool" <mbp@canonical.com> writes:
>
> Thanks for that.  We'd be interested to hear how this performs with
> emacs in general development use: is it fast enough, or what would you
> most like improved?   And are there any bugs that you hit in
> particular when using bzr with emacs?

  I speak as a simple user who likes to see what's going on in Emacs. I am hoping that Emacs can migrate to Bazaar soon because Cvs or Git are too complex for me to use and therefore hinder me from collaborating (it was not the case with Bazaar).

  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.


The old one (without merges):
-----------------------------

$ time ../bzr/bzr log >/dev/null

real	3m10.266s
user	2m57.083s
sys	0m2.004s


The new one (emacs-merges):
---------------------------

$ time ../bzr/bzr log >/dev/null

real	4m20.742s
user	4m10.092s
sys	0m2.420s


  Ok, with merges it's 1m10s more than without merges.
  However, ¿¿¿ 4m20s only to display log messages ??? That seems a lot, specially after seeing how fast can log messages be shown in other tools: here is the result for the same tree in git:

$ time git log >/dev/null

real	0m7.849s
user	0m6.940s
sys	0m0.208s


  So, having to wait 4m20s where you could be waiting 8s means that there is still room for improvement and that yes, it still is a bit uncomfortable.
  But all problems will be solved...


  Greetings,

Daniel



PS:
  The repositories I used for the tests are:
http://bzr.notengoamigos.org/emacs/trunk/
bzr://bzr.notengoamigos.org/emacs-merges/trunk/
git://git.sv.gnu.org/emacs.git




  reply	other threads:[~2008-10-21 22:07 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 [this message]
2008-10-22 18:46     ` Christian Faulhammer
2008-10-22 20:50       ` Jason Earl
2008-10-22 21:04         ` John Arbash Meinel
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=87d4htd2ll.fsf@yahoo.com \
    --to=dcl441-bugs@yahoo.com \
    --cc=bazaar@lists.canonical.com \
    --cc=emacs-devel@gnu.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).