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

Performance with Sander's DB connection caching patch for mod_dav_svn

From: Mukund <mukund_at_tessna.com>
Date: 2003-07-08 12:50:16 CEST

Hi all

Here is a quick benchmark of Sander's DB connection caching patch for
mod_dav_svn (I am also attaching a copy of the patch for 0.24.2).
We have discussed what this patch does before (if you read back on this
month's archives you will find a description of what this patch does).

Initially I had tried this on my Pentium3 laptop (Thinkpad R31 with 768 MB
of RAM) using Subversion 0.24.2 ra_dav with a Apache 2.0.46 server listening
locally. With both the client and server running on the same machine, the
performance improvements are easily between 100 - 300% and more. Since
this is not a typical real world test, I decided to repeat it with the
client and server on two different boxes and a network in between.
The client was my laptop. A 100 Mbps hub connected it to the server,
which was a dual Pentium3 workstation with 512 MB of RAM.

The results were not just as startling, but nevertheless significant.
The best part was that disk activity dropped, especially on
reads (checkouts, etc.). Anyone who has imported a large codebase into a
Subversion repository and checked it out knows how the disk goes mad.
Using a browser, when one repeatedly reloaded a file, there would be
no disk activity after the first load with the patched version (with a
browser which kept the connection open).

Results for import of CVS working copy of GIMP ~60 MB in size using svn
add + commit, and checking out the imported copy are as follows. Note
that for each test, I started with a blank repository created with

1. Client and server on the laptop

   Unpatched 0.24.2 svn commit - 31 minutes 33 seconds
   Unpatched 0.24.2 svn co - 9 minutes 39 seconds
     Patched 0.24.2 svn commit - 12 minutes 16 seconds
     Patched 0.24.2 svn co - 3 minutes 46 seconds

2. Client and server on seperate machines on 100 Mbps LAN

   Unpatched 0.24.2 svn commit - 15 minutes 24 seconds
   Unpatched 0.24.2 svn co - 4 minutes 44 seconds
     Patched 0.24.2 svn commit - 10 minutes 16 seconds
     Patched 0.24.2 svn co - 3 minutes 33 seconds

Disk activity is much lower with the patch applied, especially during
checkouts. The reason for this has been discussed on this mailing list
earlier this month.

Thank you Sander :-)


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jul 8 12:53:18 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.