You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Stefan Fuhrmann <st...@alice-dsl.de> on 2010/05/12 18:07:49 UTC

First SVN performance data

Hi there,

as I promised, I'm going to conduct some in-depth 
analysis and comprehensive SVN performance testing.
That is very time-consuming process.

However, it seems that many people have incorrect
or outdated ideas about the current state of affairs.
To add a bit more substance to the discussion, I like
to present some preliminary data and not to wait
until I collected all data I intend to. 

Side note: Maybe, these numbers make it clearer why 
my patches should be committed after review.

Bottom line: 
* SVN servers tend to be CPU-limited
  (we already observed that problem @ our company
  with SVN 1.4)
* packed repositories are ~20% faster than non-packed, 
  non-sharded
* optimal file cache size is roughly /trunk size
  (plus branch diffs, but that is yet to be quantified)
* "cold" I/O from a low-latency source takes 2 .. 3 times
  as long as from cached data
* a fully patched 1.7 server is twice as fast as 1.6.9

"Export" has been chosen to eliminate problems
with client-side w/c performance.

Please note that all measurements were taken in
a true client/server setup. You can achieve similar
performance in low-latency broad-band networks.

-- Stefan^2.



Re: First SVN performance data

Posted by Karl Heinz Marbaise <kh...@gmx.de>.
Hi,

i've tested the load performance of SVN (svnadmin load) to load a really 
large repository.

I have loaded the Apache Software Foundation Repository as dump File.

I have downloaded the svn-asf-public-r0:930176.7z (10,430,991,745 Bytes) 
which decompresses to 31,492,319,472 Bytes dump file.

I tested that with SVN 1.6.6 after the repository has been loaded the 
size has reached 27,102,279,725 Bytes

This has taken:

12 days 16 hourse 39 minutes.

I would like to know if someone else is here which has experience with 
such large loads of an SVN Repositories...

In my opinion this is a little bit slow...

Kind regards
Karl Heinz Marbaise
-- 
SoftwareEntwicklung Beratung Schulung    Tel.: +49 (0) 2405 / 415 893
Dipl.Ing.(FH) Karl Heinz Marbaise        ICQ#: 135949029
Hauptstrasse 177                         USt.IdNr: DE191347579
52146 Würselen                           http://www.soebes.de

Re: First SVN performance data

Posted by Karl Heinz Marbaise <kh...@gmx.de>.
Hi,

i've tested the load performance of SVN (svnadmin load) to load a really 
large repository.

I have loaded the Apache Software Foundation Repository as dump File.

I have downloaded the svn-asf-public-r0:930176.7z (10,430,991,745 Bytes) 
which decompresses to 31,492,319,472 Bytes dump file.

I tested that with SVN 1.6.6 after the repository has been loaded the 
size has reached 27,102,279,725 Bytes

This has taken:

12 days 16 hourse 39 minutes.

I would like to know if someone else is here which has experience with 
such large loads of an SVN Repositories...

In my opinion this is a little bit slow...

Kind regards
Karl Heinz Marbaise
-- 
SoftwareEntwicklung Beratung Schulung    Tel.: +49 (0) 2405 / 415 893
Dipl.Ing.(FH) Karl Heinz Marbaise        ICQ#: 135949029
Hauptstrasse 177                         USt.IdNr: DE191347579
52146 Würselen                           http://www.soebes.de

RE: First SVN performance data

Posted by "Bolstridge, Andrew" <an...@intergraph.com>.
> -----Original Message-----
> From: Stefan Fuhrmann [mailto:stefanfuhrmann@alice-dsl.de]
> Sent: Wednesday, May 12, 2010 7:08 PM
> To: dev@subversion.apache.org
> Subject: First SVN performance data
> 
> Hi there,
> 
> as I promised, I'm going to conduct some in-depth analysis and
> comprehensive SVN performance testing.
> That is very time-consuming process.
> 
> However, it seems that many people have incorrect or outdated ideas
> about the current state of affairs.
> To add a bit more substance to the discussion, I like to present some
> preliminary data and not to wait until I collected all data I intend
to.
> 
> Side note: Maybe, these numbers make it clearer why my patches should
be
> committed after review.
> 
> Bottom line:
> * SVN servers tend to be CPU-limited
>   (we already observed that problem @ our company
>   with SVN 1.4)


Lovely figures, but I'm guessing CPU will be more of a bottleneck when
you run on a server with 24Gb RAM and 4 SSDs in RAID-0 configuration.
The server will allocate so much to cache that everything is
super-quick, and what disk IO there is, will also be super quick. Do you
have benchmarks on a more 'representative' server? Say, a dual core with
2Gb RAM and 4 HDD disks in RAID5 running as a VM image, and SVN running
over http?