unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Lennart Borgman <lennart.borgman@gmail.com>
To: Jason Earl <jearl@notengoamigos.org>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: Surely 'bzr branch' shouldn't be this slow?
Date: Fri, 8 Jan 2010 08:10:07 +0100	[thread overview]
Message-ID: <e01d8a51001072310j2feab4a4kb25d9a7ce1ac4506@mail.gmail.com> (raw)
In-Reply-To: <87r5q1mjrp.fsf@notengoamigos.org>

On Fri, Jan 8, 2010 at 3:07 AM, Jason Earl <jearl@notengoamigos.org> wrote:
> Lennart Borgman <lennart.borgman@gmail.com> writes:
>
>> On Thu, Jan 7, 2010 at 10:48 PM, Jason Earl <jearl@notengoamigos.org> wrote:
>>> Lennart Borgman <lennart.borgman@gmail.com> writes:
>>>
>>>> On Thu, Jan 7, 2010 at 8:54 PM, Eli Zaretskii <eliz@gnu.org> wrote:
>>>>>> From: Lennart Borgman <lennart.borgman@gmail.com>
>>>>>> Date: Thu, 7 Jan 2010 09:37:15 +0100
>>>>>> Cc: emacs-devel@gnu.org
>>>>>>
>>>>>> Just a comment: I have not even tried yet to use bzr. According to
>>>>>> what I am reading it looks impossible at the moment.
>>>>>>
>>>>>> Am I right or?
>>>>>
>>>>> It's both possible and practical.  I use it on 2 different Windows
>>>>> machines and on 1 GNU/Linux one, and it works quite well.  The initial
>>>>> "bzr branch" takes a long time, but that's all.
>>>>
>>>>
>>>> And with a 2Mbit/s connection and an Alan style pc, 1GB RAM?
>>>
>>> I use it with a netbook with 1GB of Ram and no swap.  It works fine.  I
>>> will admit that I have switched to pulling from launchpad, but I did my
>>> initial pull from Savannah.
>>
>> How long did the initial pull take on this machine? (Sorry if you have
>> told already. Are the figures perhaps on the wiki?) How fast is your
>> internet?
>
> Just for fun I did it again into a new repository.  While there were
> times when my netbook struggled, for the most part it appeared that my
> crappy wireless network connection was the bottleneck.
>
> time bzr branch http://bzr.savannah.gnu.org/r/emacs/trunk/ trunk
> Branched 99273 revision(s).
>
> real    56m30.346s
> user    34m10.160s
> sys     0m32.638s
>
> Then I tested to see how long it took to see if there were more
> revisions.  There weren't any.
>
> time bzr pull
> Using saved parent location: http://bzr.savannah.gnu.org/r/emacs/trunk/
> No revisions to pull.
>
> real    0m8.109s
> user    0m1.672s
> sys     0m0.272s
>
> This is on a wireless network.
>
>> And doing the initial pull from Launchpad instead how much faster is it?
>
> Launchpad actually took at little longer:
>
> time bzr pull --remember lp:emacs
> No revisions to pull.
>
> real    0m10.246s
> user    0m1.108s
> sys     0m0.180s
>
> The advantage of using launchpad is that you will never get the
> pathologically bad updates where bzr pulls down 100M of data to make 2M
> worth of changes.  The disadvantage is that it is a mirror that updates
> only every 8 hours.


Thanks Jason, very clear and instructive. The road for me at the
moment seems to be Launchpad. The 8 hours does not matter right now,
but the the 100 MB does.




  reply	other threads:[~2010-01-08  7:10 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-03 17:47 Surely 'bzr branch' shouldn't be this slow? 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-06 18:23         ` Eli Zaretskii
2010-01-06 20:21           ` Stefan Monnier
2010-01-07  7:44           ` Yavor Doganov
2010-01-07  8:37             ` Lennart Borgman
2010-01-07  9:31               ` Juanma Barranquero
2010-01-07 19:18               ` Stephen Berman
2010-01-07 19:54               ` Eli Zaretskii
2010-01-07 20:09                 ` Lennart Borgman
2010-01-07 21:48                   ` Jason Earl
2010-01-07 23:48                     ` Lennart Borgman
2010-01-08  2:07                       ` Jason Earl
2010-01-08  7:10                         ` Lennart Borgman [this message]
2010-01-08  8:13                   ` Eli Zaretskii
2010-01-07 14:46             ` Stefan Monnier
2010-01-07 17:05               ` Yavor Doganov
2010-01-07 19:43                 ` Stefan Monnier
2010-01-07 19:46                   ` Lennart Borgman
2010-01-07 20:26                     ` Thrashing [was: Surely 'bzr branch' shouldn't be this slow?] Stephen J. Turnbull
2010-01-07 20:20                       ` Lennart Borgman
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
2010-01-06 14:37     ` Surely 'bzr branch' " Stefan Monnier
2010-01-07  5:00     ` Karl Fogel

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=e01d8a51001072310j2feab4a4kb25d9a7ce1ac4506@mail.gmail.com \
    --to=lennart.borgman@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=jearl@notengoamigos.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).