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

Re: KeepAlive on Apache and Subversion

From: Jeremy Whitlock <jcscoobyrs_at_gmail.com>
Date: Wed, 1 Apr 2009 12:30:06 -0600

> What is the official Subversion setting for KeepAlive? Should this be
> on or off? How does it affect Subversion. We use Apache's httpd as a
> server for our Subversion repository and this HTTP server is not used
> for anything but Subversion.

The "KeepAlive" in Apache does have an impact on Subversion. If you
have KeepAlive off, you end up with multiple Apache connections being
used to serve your single Subversion request. That means that for
each connection created, you reauthenticate. If you have a custom
authentication/authorization mechanism in place, like a custom Apache
module or using mod_[perl|python|etc.] to handle your Subversion
authn/authz, you end up reauthenticating unnecessarily because your
cache scope in Apache for modules is usually in the connection pool.
So...you should see a jump in performance with KeepAlive on. This
does not mean the user is prompted to reauthenticate but the logic
used to authenticate a user can be reran if your Subversion operation
uses multiple connections. In a situation where you use the network
to authenticate, like ldap/database/web services/etc., this can be a
performance hit.

Take care,
Jeremy Whitlock
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-04-01 20:50:32 CEST

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