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

Poor Performance - Subversion 1.1.0 and Apache 2.0.50/2.0.52 on Windows 2000

From: Tony Butt <tjb_at_cea.com.au>
Date: 2004-10-12 03:38:07 CEST

We have been running the subversion 1.0.x series with Apache 2.0.48, then Apache 2.0.50 on W2000 SP3 for some months, and have recently encountered a major problem.

I recently updated our subversion server to 1.1.0 from 1.1.0 rc3
At the same time, I updated my client to TortoiseSVN 1.1.0, from the prior RC.

My first sympton was that when using the repo-browser with Tortoise, the performance was poor, and sometimes just failed to return. At the same time, the apache process on the W2K repository server would spin, growing in size to 24M or so, and consuming 100% CPU for an extended period of time.

I first suspected Tortoise, and reverted to a prior version, giving the same problem.

I tried a vendor merge of a source tree from the command line, as I have done several times in the past. It ran very slowly, exhibiting the same apache server problem, and at some point failed(!) I have totally reinstalled apache, updating to 2.0.52 from 2.0.50, reinstalled subversion on the server, and this problem persists. I checked the repository with svnadmin, and everything is Ok.

Access to the repository works fine via file:/// or svn:/// protocols. Strangely enough, web browser access seems to work OK

I have even swapped in a backup of the repository, and still have the same problem.

For the time being, we will limp along with svn: protocol access, but we would much prefer to use the apache server.

Is there some apache configuration I should look at, or is this a real bug with the subversion apache modules.

Tony Butt
CEA Technologies
Canberra
Australia
Received on Tue Oct 12 09:23:31 2004

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.