Login | Register
My pages Projects Community openCollabNet

Discussions > users [DISABLED] > Re: KeepAlive on Apache and Subversion

subversion
Discussion topic

Back to topic list

Re: KeepAlive on Apache and Subversion

Author jwhitlock
Full name Jeremy Whitlock
Date 2009-04-01 11:30:07 PDT
Message > 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
http://www.thoughtspark.org

« Previous message in topic | 2 of 13 | Next message in topic »

Messages

Show all messages in topic

KeepAlive on Apache and Subversion David Weintraub <qazwart at gmail dot com> David Weintraub <qazwart at gmail dot com> 2009-04-01 09:35:30 PDT
     Re: KeepAlive on Apache and Subversion jwhitlock Jeremy Whitlock 2009-04-01 11:30:07 PDT
         1.6.2 poor commit performance with large data "Bolstridge, Andrew" <andy dot bolstridge at intergraph dot com> "Bolstridge, Andrew" <andy dot bolstridge at intergraph dot com> 2009-05-29 02:58:02 PDT
             Re: 1.6.2 poor commit performance with large data bpsm B. Smith-Mannschott 2009-05-29 03:26:51 PDT
                 RE: 1.6.2 poor commit performance with large data "Bolstridge, Andrew" <andy dot bolstridge at intergraph dot com> "Bolstridge, Andrew" <andy dot bolstridge at intergraph dot com> 2009-06-02 10:24:57 PDT
                     Re: 1.6.2 poor commit performance with large data markphip Mark Phippard 2009-06-02 10:31:26 PDT
                         Re: 1.6.2 poor commit performance with large data ajustinjohnson Justin Johnson 2009-06-04 11:14:02 PDT
                         Re: 1.6.2 poor commit performance with large data ajustinjohnson Justin Johnson 2009-06-08 09:03:09 PDT
                             Re: 1.6.2 poor commit performance with large data ajustinjohnson Justin Johnson 2009-06-08 11:57:33 PDT
                                 Re: 1.6.2 poor commit performance with large data stsp Stefan Sperling 2009-06-09 03:37:29 PDT
                             Re: 1.6.2 poor commit performance with large data ajustinjohnson Justin Johnson 2009-06-09 10:50:36 PDT
                                 Re: 1.6.2 poor commit performance with large data markphip Mark Phippard 2009-06-09 10:54:03 PDT
                                     Re: 1.6.2 poor commit performance with large data ajustinjohnson Justin Johnson 2009-06-09 10:54:53 PDT
Messages per page: