From: Eli Zaretskii <eliz@gnu.org>
To: Kevin Ryde <user42@zip.com.au>
Cc: emacs-devel@gnu.org
Subject: Re: bazaar: "unable to obtain lock"
Date: Mon, 04 Jan 2010 02:05:48 -0500 [thread overview]
Message-ID: <E1NRh0e-0002kF-IR@fencepost.gnu.org> (raw)
In-Reply-To: <87fx6m7r18.fsf@blah.blah> (message from Kevin Ryde on Mon, 04 Jan 2010 09:38:27 +1100)
> From: Kevin Ryde <user42@zip.com.au>
> Date: Mon, 04 Jan 2010 09:38:27 +1100
>
> Óscar Fuentes <ofv@wanadoo.es> writes:
> >
> > A simple update after a few days can easily require to transfer 10 MB.
>
> Ah, thanks, that'd be very borderline. If it's potentially every commit
> then it's a killer. I wonder if the wiki could put the requirements up
> front a bit more. Without being too provocative something like
>
> The repo is about 300Mb. An initial checkout will download it in
> full and may use about 1Gb of RAM while doing so. Subsequent
> commits and updates could transfer as much as 10Mb even for modest
> changes.
But the last sentence could be blatantly misleading, it seems. For
example, today's "bzr up" crams 185MB(!) of data through the wire.
And that's only according to the progress indicator; who knows what
else is going on on the protocol level? My previous update was 16
hours ago, and the files actually changed on the trunk since then are
just a few:
M lisp/ChangeLog
M lisp/vc-bzr.el
M src/ChangeLog
M src/dbusbind.c
It sounds like such a massive update is due to the change in the
branches configuration in the repository: most of the branches were
moved to the old-branches and other-branches ``subdirectories''.
Maybe this is a very infrequent situation, but it does show the
potential.
So I'm not sure if we should tell anything about traffic beyond the
initial branch, whose size is more or less known and changes very
slowly.
next prev parent reply other threads:[~2010-01-04 7:05 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-29 23:53 bazaar: "unable to obtain lock" Robert J. Chassell
2009-12-30 3:39 ` Karl Fogel
2009-12-30 15:15 ` Robert J. Chassell
2009-12-31 19:14 ` Karl Fogel
2010-01-01 0:19 ` Robert J. Chassell
2009-12-31 19:15 ` Karl Fogel
2009-12-30 16:43 ` Robert J. Chassell
2009-12-30 17:25 ` Andreas Schwab
2009-12-30 21:46 ` Robert J. Chassell
2009-12-30 22:18 ` Andreas Schwab
2009-12-31 1:48 ` Robert J. Chassell
2009-12-31 4:29 ` Óscar Fuentes
2009-12-31 6:59 ` Óscar Fuentes
2009-12-31 11:32 ` Robert J. Chassell
2009-12-31 14:57 ` James Cloos
2009-12-30 23:34 ` Kevin Ryde
2009-12-31 0:30 ` Óscar Fuentes
2009-12-31 0:44 ` Lennart Borgman
2009-12-31 1:07 ` Óscar Fuentes
2009-12-31 1:24 ` Lennart Borgman
2010-01-03 22:38 ` Kevin Ryde
2010-01-04 7:05 ` Eli Zaretskii [this message]
2010-01-05 21:20 ` Kevin Ryde
2010-01-01 9:59 ` Stephen J. Turnbull
2010-01-01 10:16 ` Óscar Fuentes
2010-01-01 16:42 ` Jason Earl
2009-12-30 9:19 ` David Kastrup
-- strict thread matches above, loose matches on Subject: below --
2009-12-29 17:14 Juanma Barranquero
2009-12-29 17:40 ` Karl Fogel
2009-12-29 17:44 ` Juanma Barranquero
2009-12-29 18:42 ` Karl Fogel
2009-12-29 20:39 ` Juanma Barranquero
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=E1NRh0e-0002kF-IR@fencepost.gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=user42@zip.com.au \
/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.