From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: emacs-devel@gnu.org
Subject: Re: "bzr commit" takes 17 minutes?
Date: Fri, 25 Feb 2011 13:05:53 +0200 [thread overview]
Message-ID: <83mxlkqsq6.fsf@gnu.org> (raw)
In-Reply-To: <4D67836F.9090504@cs.ucla.edu>
> Date: Fri, 25 Feb 2011 02:24:47 -0800
> From: Paul Eggert <eggert@cs.ucla.edu>
>
> When I do even trivial bzr commits to the Emacs trunk
> it takes an amazingly long time:
>
> > $ time bzr commit -m 'Elaborate my most-recent ChangeLog entry.'
> > Committing to: bzr+ssh://eggert@bzr.savannah.gnu.org/emacs/trunk/
> > modified ChangeLog
> [here is where the long delay occurs]
> > Committed revision 103419.
> >
> > real 17m33.115s
> > user 0m0.390s
> > sys 0m0.170s
Can you show the corresponding trace from your ~/.bzr.log?
> Are other committers observing such bad performance?
Not that long, never. A commit is typically 1-2 min for me. Which is
also slow, but not as bad as 17 min. Is the above time exceptional,
or do you get that as a matter of routine? You can gather statistics
from your ~/.bzr.log file.
next prev parent reply other threads:[~2011-02-25 11:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-25 10:24 "bzr commit" takes 17 minutes? Paul Eggert
2011-02-25 10:47 ` Andreas Schwab
2011-02-25 11:08 ` Eli Zaretskii
2011-02-25 11:05 ` Eli Zaretskii [this message]
2011-02-25 11:23 ` Eli Zaretskii
2011-02-25 11:51 ` Eli Zaretskii
2011-02-25 12:01 ` Eli Zaretskii
2011-02-25 17:46 ` Glenn Morris
2011-02-26 4:30 ` Miles Bader
2011-02-25 18:30 ` Savannah slowdown due to cgit.cgi [was Re: "bzr commit" takes 17 minutes?] Glenn Morris
2011-02-26 0:45 ` Andrew W. Nosenko
2011-02-26 7:10 ` Eli Zaretskii
2011-02-25 17:41 ` "bzr commit" takes 17 minutes? Thierry Volpiatto
2011-02-25 17:59 ` Eli Zaretskii
2011-02-25 18:13 ` Thierry Volpiatto
2011-02-25 18:55 ` Eli Zaretskii
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=83mxlkqsq6.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=eggert@cs.ucla.edu \
--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).