[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: issue #1429 progress: ra_dav changing analogously to ra_svn

From: <kfogel_at_collab.net>
Date: 2003-10-28 02:09:23 CET

Tobias Ringström <tobias@ringstrom.mine.nu> writes:
> This change is great, because it completely removes the (unneccessary)
> latency performance problem. Unfortunately this does not tell us that
> SVN is faster than CVS, as one might think from the numbers abobe.
> The only reason SVN is faster here is because it compresses the data.
> If you enable comression for CVS, the time will be very close to SVN
> time.

Compressed CVS is actually faster (I didn't include those numbers, not
because I wanted to mislead anyone, but just because I didn't want to
add distractions to an already complex mail). With -z3, the same CVS
checkouts were averaging 33 seconds or so.

> If you increase the bandwidth, there comes a point where the checkout
> time does not go below a certain time becuse the server cannot
> generate data to transmit any faster, or because libsvn_wc cannot
> write the data any faster. The throughput at that point is the real
> performance limit, and I fear that CVS will still beat SVN by a wide
> margin there.

You are right. I already know this from doing the same tests over
ra_dav on localhost.

> Perhaps that sounded negative, but there is still reason to be glad,
> becuse from my own tests I can see that SVN can saturate a 2 Mbit link
> without even breaking a sweat. That means that it is fast enough for
> a lot of Internet applications, and at least to me, that is great news!

Yeah. It would be nice someday to beat CVS even in LAN performance --
but acceptable WAN performance is a first step, anyway! :-)


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Oct 28 02:48:03 2003

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.