From: grischka <grishka@gmx.de>
To: stephen@xemacs.org
Cc: emacs-devel@gnu.org
Subject: Re: Surely 'bzr update' shouldn't be this slow?
Date: Fri, 08 Jan 2010 00:29:09 +0100 [thread overview]
Message-ID: <4B466E45.7060706@gmx.de> (raw)
> > It IS copying, conceptually
>
> Alan, don't be contrary. Óscar is just telling you the facts, and
> AIUI *he* would not have chosen bzr if it were up to him. He's just
> trying to help you and others make the best use of the official VCS.
But Óscar wasn't telling any facts aside from that the issue is maybe
"complex" and "non-trivial".
> No, it has to do a lot more than that.
Has to? Why?
> What it is doing is
> conceptually most like garbage collection. The actual content of a
> repository is stored as a set of compressed archives of file objects,
> revision objects, and patches, plus some indicies. (These archives
> are called "packs.") The "processing" goes through those objects,
> throws out the ones not needed for the branch you request, and
> reconstructs minimal packs and indicies for them.
So it's slow because it does lots of slow stuff. Fine.
Obviously compression is slow, but who says it needs to de/recompress
the objects just to build a new index or to build a new pack with some
but not all of the objects?
Also with http: You claim it's slow because it needs to download entire
packs. But AFAIK http supports seeking into file offsets. Or otherwise
you can store the top of the history near the beginning of the pack such
that you can stop downloading as soon as you have the missing updates.
Or otherwise you could have packs on the server only for commits older
than a year and anything more recent as single files. It's not that
there weren't alternatives.
--- grischka
next reply other threads:[~2010-01-07 23:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-07 23:29 grischka [this message]
2010-01-08 5:57 ` Surely 'bzr update' shouldn't be this slow? Stephen J. Turnbull
2010-01-08 17:49 ` grischka
-- strict thread matches above, loose matches on Subject: below --
2010-01-03 17:47 Surely 'bzr branch' " Alan Mackenzie
2010-01-03 17:59 ` Óscar Fuentes
2010-01-06 13:10 ` Alan Mackenzie
2010-01-06 13:28 ` Jason Rumney
2010-01-06 14:06 ` Óscar Fuentes
2010-01-07 13:40 ` Surely 'bzr update' shouldn't be this slow? [was: branch] Alan Mackenzie
2010-01-07 13:56 ` Surely 'bzr update' shouldn't be this slow? Óscar Fuentes
2010-01-07 14:03 ` Lennart Borgman
2010-01-07 15:18 ` Jan Djärv
2010-01-07 14:52 ` Alan Mackenzie
2010-01-07 15:00 ` Juanma Barranquero
2010-01-07 15:17 ` Karl Fogel
2010-01-07 17:51 ` Glenn Morris
2010-01-07 20:48 ` Karl Fogel
2010-01-07 21:21 ` Glenn Morris
2010-01-08 8:48 ` Eli Zaretskii
2010-01-07 15:17 ` Óscar Fuentes
2010-01-07 17:54 ` Stephen J. Turnbull
2010-01-07 15:06 ` 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=4B466E45.7060706@gmx.de \
--to=grishka@gmx.de \
--cc=emacs-devel@gnu.org \
--cc=stephen@xemacs.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.