From: "Stephen J. Turnbull" <stephen@xemacs.org>
To: Lennart Borgman <lennart.borgman@gmail.com>
Cc: "Óscar Fuentes" <ofv@wanadoo.es>, emacs-devel@gnu.org
Subject: Re: Listing branches with bzr
Date: Wed, 02 Dec 2009 12:53:47 +0900 [thread overview]
Message-ID: <87ws16uj3o.fsf@uwakimon.sk.tsukuba.ac.jp> (raw)
In-Reply-To: <e01d8a50912011817g40381a67g54f1d3ea815bc96f@mail.gmail.com>
Lennart Borgman writes:
> Isn't it doing the same work as on the server?
Yes.
> Is it the network traffic that makes it so incredibly slow?
Yes. What you are seeing is bzr using algorithms designed on the
assumption that files are local on each individual file via HTTP.
> I am thinking about Stephens reply (which I have not had time to
> respond to). He mentioned that git uses SHA to identify files why bzr
> does not do that? Is that the cause of the time trouble we are seeing?
As I wrote before, bzr uses a way to identify files that makes
tracking file and directory renames precise and efficient (in git
there is some imprecision and much slower). For most other purposes,
the bzr file-tracking method and the git content-tracking method lead
to equivalent results with varying degrees of efficiency. For a few
things git is quite a bit faster, but bzr is not unusable.
In any case it is not the cause of this slowdown. The cause here
slowdown is that many files are being downloaded by HTTP, and this
would be also be true to some extent for git. The big difference is
that for some reason Savannah admins think that use of git's smart
server is acceptable, security-wise, but they don't like bzr's.
Hopefully that can be changed soon, but to get things done in time for
the Emacs VCS switch probably only a request from Richard will do.
The Savannah admins don't currently consider installation of the smart
server a high priority (there's an open SR, and they've explicitly
said, "not now, and not soon").
> I would consider that just as serious as a bug. But maybe there is
> something I do not understand there.
There is. Don't worry about it. This is an administrative problem,
not a technical deficiency in bzr.[1] Stefan and Karl are on this,
and they're getting help on the technical details that the Savannah
hackers need to know from senior bzr developers. And you'll soak up
the technical knowledge as you use bzr; it's not something you need to
know to get started.
Footnotes:
[1] Unless you consider having *both* a smart, efficient server and a
very easy way for any Joe Hacker with a home page to give others
access to his bzr branch a bad thing. :-)
next prev parent reply other threads:[~2009-12-02 3:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-01 19:06 Listing branches with bzr Eli Zaretskii
2009-12-01 21:46 ` Karl Fogel
2009-12-01 21:57 ` Xavier Maillard
2009-12-01 22:20 ` Jason Earl
2009-12-02 1:57 ` Lennart Borgman
2009-12-02 2:13 ` Óscar Fuentes
2009-12-02 2:17 ` Lennart Borgman
2009-12-02 2:44 ` Óscar Fuentes
2009-12-02 3:53 ` Stephen J. Turnbull [this message]
2009-12-02 6:21 ` Eli Zaretskii
2009-12-02 13:45 ` Martin Albisetti
2009-12-01 21:55 ` Stefan Monnier
2009-12-01 22:00 ` Dan Nicolaescu
2009-12-02 4:19 ` Eli Zaretskii
2009-12-02 23:24 ` Xavier Maillard
2009-12-03 3:55 ` Eli Zaretskii
2009-12-01 22:08 ` Alexander Belchenko
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=87ws16uj3o.fsf@uwakimon.sk.tsukuba.ac.jp \
--to=stephen@xemacs.org \
--cc=emacs-devel@gnu.org \
--cc=lennart.borgman@gmail.com \
--cc=ofv@wanadoo.es \
/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).