unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: rms@gnu.org
Cc: emacs-devel@gnu.org
Subject: Re: Is bzr+ssh's speed satisfactory?
Date: Sat, 16 Oct 2010 09:49:17 +0200	[thread overview]
Message-ID: <83hbgmbmrm.fsf@gnu.org> (raw)
In-Reply-To: <E1P6ys5-000480-7n@fencepost.gnu.org>

> From: Richard Stallman <rms@gnu.org>
> Date: Sat, 16 Oct 2010 00:59:53 -0400
> 
> bzr was slow on savannah due to the use of sftp.
> Do people find bzr satisfactory now?

It is significantly faster, especially with frequent updates.  Where
previously I had to wait up to 5-6 minutes for an update of 3-4 days
worth of development, now it's down to 1-2 minutes or so, depending on
the amount of files that were modified.  Where previously it took 2
minutes to update a few files that were modified during several hours
since the last update, it now takes 25 seconds.  Previously it would
take about 40 seconds to get the "tree is up to date" result; now it
takes 10 to 15.

This is with a 3.5Mbps link, with other jobs running on the same
machine and using the link simultaneously.

I don't remember the exact timings of CVS, but I think the numbers are
comparable, perhaps even slightly faster.



  parent reply	other threads:[~2010-10-16  7:49 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-16  4:59 (no subject) Richard Stallman
2010-10-16  6:08 ` Werner LEMBERG
2010-10-16  6:10   ` Werner LEMBERG
2010-10-16  7:54     ` Is bzr+ssh's speed satisfactory? Eli Zaretskii
2010-10-16  7:52   ` Eli Zaretskii
2010-10-18  6:26   ` (no subject) Richard Stallman
2010-10-16  7:49 ` Eli Zaretskii [this message]
2010-10-19 18:28 ` Glenn Morris
2010-10-19 18:43   ` bzr on Savannah Glenn Morris
2010-10-19 18:58     ` Eli Zaretskii
2010-10-19 19:03       ` Glenn Morris
2010-10-24  3:54     ` Richard Stallman
2010-10-24 19:50       ` Glenn Morris

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=83hbgmbmrm.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=rms@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 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).