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

Re: Slow performance using http:// vs. svn://

From: Erik Huelsmann <ehuels_at_gmail.com>
Date: 2007-04-02 20:59:44 CEST

On 4/2/07, David Ferguson <ferguson.david@gmail.com> wrote:
> Hi all,
> I am working with my company's IT department to setup a Subversion server so
> that we can evaluate switching from CVS to Subversion. IT would like us to
> use an Apache server for repository access. However, the performance is
> pretty bad compared to just running svnserve. A fresh checkout using
> http:// takes 3:24 while checking out the same repository using svn:// takes
> 1:47. At first I suspected that Apache's LDAP authentication was slowing
> things down, but I had them disable authentication with little change in the
> checkout time.
> Any idea why http:// would be so much slower than svn:// ? Is this
> expected? Can you recommend any change to the Apache configuration to speed
> things up?

The svn protocol is statefull and tailored for use by svn.

The HTTP protocol is stateless and defined as the more general-use
WebDAV protocol.

So, yes, because of these reasons (and some others), there's an
expected speed difference in favor of svn://. How big it should be or
whether your config can be tweaked better, I don't know.

I'm not sure Serf supports LDAP, but have you tried performance checks
with the Serf HTTP client library? There should be measurable
performance benefits from using Serf.



To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Apr 2 21:00:13 2007

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