I think the reason is somewhere at the connection-specific configuration of apache in interaction with the behaviour of the subversion-client (which may has also connection-options...?).
I suspect the KeepAlive-Handing... it seems that the subversion-client closes its connection between checking the different "externals" (which are on the same server) and the server keeps the connection opened and waits for further data. Until the connection is finally closed by timeout the server does NOT handle the request regarding the next "external". I don't have a clue why the server simply isn't accepting a second connection for the same client while the first connection is waiting for its timeout... I think one of the following options can affect this behaviour, but I'm still searching for an option which sounds like "ConnectionsPerClient": MaxRequestsPerChild KeepAliveTimeout Note: We are using a https-Connection. -------- Original-Nachricht -------- > Datum: Wed, 25 Jan 2012 14:35:33 -0600 > Von: Ryan Schmidt <subversion-20...@ryandesign.com> > An: d.guthm...@gmx.net > CC: users@subversion.apache.org > Betreff: Re: Checkout slow without proxy > > On Jan 25, 2012, at 03:43, d.guthm...@gmx.net wrote: > > > We are using Subversion 1.5.1 on Apache 2.2 on the server-side > > As a first step, you should upgrade the Subversion software on your > server. Subversion 1.5.x and earlier are not supported anymore. > > http://subversion.apache.org/docs/release-notes/1.7.html#svn-1.5-deprecation > > -- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de
