From: Shachar Shemesh <lkml@shemesh.biz>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Ben Collins <bcollins@debian.org>,
Larry McVoy <lm@work.bitmover.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: BK->CVS, kernel.bkbits.net
Date: Sun, 20 Apr 2003 16:47:09 +0300 [thread overview]
Message-ID: <3EA2A4DD.2080809@shemesh.biz> (raw)
In-Reply-To: <Pine.GSO.4.21.0304201157280.14680-100000@vervain.sonytel.be>
Geert Uytterhoeven wrote:
>On Sun, 20 Apr 2003, Shachar Shemesh wrote:
>
>
>>The idea is that it uses the full duplexity of the channel to get client
>>
>>
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
>
>>side information about the repository on that end while downloading
>>changes, thus increasing the effective bandwidth. It only falls back to
>>
>>
>
>What does this mean for asymmetric links (ADSL or cable)?
>
>Gr{oetje,eeting}s,
>
> Geert
>
>
ADSL is still full duplex, just not symetrical.
If I understand cvsup's operation enough, it uses the fact it
understands what a CVS repository is to send to the server the revisions
available for a given file. The lets the server know which parts of the
file it needs to send back. The uplink side receives a very low
utilization compared to the downlink side. In practice, I'm using cvsup
for the Wine repository over an ADSL (1.5M down, I don't remeber whether
it's 64 or 128K up), and am very pleased from it. Admitebly, I was not a
very enthusiastic rsync convert, so I can't tell you how much faster
cvsup is.
If you want an official benchmark, you'll have to wait a few days for my
Wine rep. to fall out of synch. I should note the cvsup is useless if
all your'e going to do is get the initial version. If I recall
correctly, it actually use rsync to transfer files it cannot parse as
CVS files, which means that initial repository retrieval should be
equally fast with both.
--
Shachar Shemesh
Open Source integration consultant
Home page & resume - http://www.shemesh.biz/
next prev parent reply other threads:[~2003-04-20 13:36 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-17 16:27 BK->CVS, kernel.bkbits.net Larry McVoy
2003-04-17 20:52 ` H. Peter Anvin
2003-04-20 0:30 ` Larry McVoy
2003-04-20 13:16 ` Roman Zippel
2003-04-20 15:23 ` Larry McVoy
2003-04-20 15:42 ` Roman Zippel
2003-04-21 4:46 ` Neil Brown
2003-04-21 6:58 ` Jeff Garzik
2003-04-23 15:49 ` Carl-Daniel Hailfinger
2003-04-24 2:45 ` Larry McVoy
2003-04-24 7:21 ` Christoph Hellwig
2003-04-24 9:19 ` Carl-Daniel Hailfinger
2003-04-21 15:58 ` Jamie Lokier
2003-04-20 1:34 ` Ben Collins
2003-04-20 1:49 ` Larry McVoy
2003-04-21 18:58 ` H. Peter Anvin
2003-04-21 21:41 ` Ben Collins
2003-04-20 7:32 ` Shachar Shemesh
2003-04-20 9:58 ` Geert Uytterhoeven
2003-04-20 13:47 ` Shachar Shemesh [this message]
2003-04-20 13:01 ` Ben Collins
2003-04-20 13:37 ` Shachar Shemesh
2003-04-20 13:42 ` viro
2003-04-20 13:47 ` Ben Collins
2003-04-20 14:13 ` Shachar Shemesh
2003-04-20 14:42 ` Shachar Shemesh
2003-04-20 14:47 ` Wichert Akkerman
2003-04-20 14:58 ` Shachar Shemesh
2003-04-20 15:45 ` viro
2003-04-22 11:09 ` Gerd Knorr
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=3EA2A4DD.2080809@shemesh.biz \
--to=lkml@shemesh.biz \
--cc=bcollins@debian.org \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lm@work.bitmover.com \
/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.
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 NNTP newsgroup(s).