> seanc@dimensionalrift.com writes:
>
>> Timings:
>> local svnserve: 0m 10s
>> local file: 0m 9s
>> local http: 3m 33s
>> local https: 3m 33s
>>
>> remote svnserve: 0m 11s
>> remote http: 3m 32s
>> remote https: 3m 33s
>>
>> Is there some magic apache2 setting I've missed somewhere?. I've played
>> with turning AuthType off (as well as SSL) and they have no effect on
>> the
>> performance of subversion.
>
> There are some known ra_dav performance issues, issue 773 in
> particular. The first thing to determine is whether the problem is
> excessive CPU use or whether it is some sort of IO problem.
>
> First, make sure nothing other than your subversion client is
> accessing the apache server, and then run something like
>
> $ ps aux | grep [h]ttpd
>
> before and after an ra_dav checkout. This will let you see the amount
> of CPU used by the apache processes. If apache only uses a few
> seconds of CPU then the problem is probably some sort of IO delay. If
> apache uses 3 minutes of CPU then we have some sort of scaling
> problem.
>
apache2 accumulated cpu time from a clean start and svn checkout, is
listed as 9 seconds. Watching with top, the active apache2 thread sits
around 1.8-3.8% cpu usage (which matches the 20x speed difference I am
seeing between ra_svn and ra_dav), and every now and then I catch its cpu
spiking up to 10% (very rare though). Memory is pretty low, with an
occasional spike up to 20MB.
I would be willing to go with the ra_svn approach but it doesnt seem
possible to secure it in a meaningful manner for a multi-user
configuration. Perhaps if svnserve were to run exclusively on 127.0.0.1
and a proxy program (say, svnproxy) could be executed via rsh or plink
from my clients I could at least secure it in the same way as CVS.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Feb 25 20:57:12 2003