From: Eli Zaretskii <eliz@gnu.org>
To: David Reitter <david.reitter@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: 23 branch - can't push - lock
Date: Thu, 16 Jun 2011 23:09:39 +0300 [thread overview]
Message-ID: <83aadhy1vg.fsf@gnu.org> (raw)
In-Reply-To: <65EAEB6A-294A-4B8F-8BCA-F37C5914E5D6@gmail.com>
> From: David Reitter <david.reitter@gmail.com>
> Date: Thu, 16 Jun 2011 13:44:46 -0400
> Cc: emacs-devel@gnu.org
>
> How do I tell it's a local lock? I don't have /srv/bzr.
Then I was mistaken, and it's not local. I assume that when you said
"there's a lock", you had evidence there indeed was a lock.
> I thought that was on the server. No, I didn't do C-c. I have since pushed to bzr+ssh, so perhaps the problem was one of authentication, and really just permissions on the server.
Maybe. I always use bzr+ssh.
> dr@elin:~/Projects/emacs/emacs-23 $ time bzr log >/dev/null
> real 0m33.780s
Why in the world would you need the log of all the 104K revisions?
Btw, I suggest to set up a bzr alias so that "log" is actually
"log --line", it's much more concise and faster, too.
> First page only:
> real 0m3.594s [faster when repeated,i.e., in cache]
What kind of machine is that? On my 6-year-old Windows box with a
single 3 GHz core, I get this:
D:\gnu\bzr\emacs\trunk>timep bzr --no-plugins log -l40 > nul
real 00h00m00.437s
user 00h00m00.343s
sys 00h00m00.078s
D:\gnu\bzr\emacs\trunk>timep bzr log -l40 > nul
real 00h00m00.812s
user 00h00m00.500s
sys 00h00m00.281s
And anyway, 3.5 sec is hardly significantly different from 0.8, for
producing something that a human needs to _read_.
> dr@elin:~/em23 emacs23$ time git log >/dev/null
> real 0m5.427s
Irrelevant. But OTOH, this is _very_ relevant for my work on the
display engine:
D:\gnu\bzr\emacs\trunk>timep bzr annotate src/xdisp.c > nul
real 00h01m23.421s
user 00h01m18.734s
sys 00h00m03.046s
eliz@fencepost:~/git/emacs$ time git annotate src/xdisp.c > /dev/null
real 8m28.865s
user 7m45.490s
sys 0m6.090s
(The second timing is from fencepost.gnu.org, a multicore x86_64
server that is much faster than what I have here.)
> The merge of a single revision (-c) also took a long time.
How long is "long" in this case? (You can look it up in your
~/.bzr.log file, it logs the time and network throughput/speed of each
command, something I've searched high and low in git and couldn't
find.)
next prev parent reply other threads:[~2011-06-16 20:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-16 15:49 23 branch - can't push - lock David Reitter
2011-06-16 16:28 ` David Reitter
2011-06-16 21:44 ` Glenn Morris
2011-06-16 17:27 ` Eli Zaretskii
2011-06-16 17:44 ` David Reitter
2011-06-16 20:09 ` Eli Zaretskii [this message]
2011-06-17 13:57 ` David Reitter
2011-06-17 15:39 ` Eli Zaretskii
2011-06-17 19:19 ` UI / reaction time - was: " David Reitter
2011-06-17 21:59 ` chad
2011-06-19 13:42 ` Stephen J. Turnbull
2011-06-17 16:30 ` Stefan Monnier
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83aadhy1vg.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=david.reitter@gmail.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.