RE: Svn update slow for a small repository

As a follow up I should've mentioned that my repository is in FSFS format, not BDB.
 
One thing I'm curious about is that in the repository there happens to be a fair number of binary files, mostly PNG files which are web-assets. However, some of these PNG files are really large because some of them are graphic mockups. Could that seriously slow down doing updates? I wouldn't think so as I'm assuming it does some quick check on a binary file to see if it has a different revision number?
 
Thanks,
Christian

________________________________

From: Cabanero, Christian [mailto:cabanero@amazon.com]
Sent: Tuesday, March 14, 2006 2:19 PM
To: users@subversion.tigris.org
Subject: Svn update slow for a small repository

Hello,

We're trying to use subversion 1.3.0 for a pretty small repository and are having intermittent performance problems with it.

The server is a Linux RHEL 3 box that currently is running nothing but subversion server 1.3.0. However, I'm running it using the "svnserve -d" mode and it's being accessed via svn:// protocol only. No one on the team is using http:// <http://> or direct file access. The repository is pretty small. The db directory is only 70 MB, and most of that is likely large binary png files that we were using for mock-ups.

Right now everyone on the team (6 people) is using subversion version 1.3.0, using both svn command line and also the subclipse plug-in which in-turn is using the JavaSVN library. Both the command line and plug-in is intermittently slow, sometimes very slow.

I also have a FishEYE server that is scanning the repository periodically however even when I have that turned off it is still slow, although turning it off appears to help a little bit.

The slowness is most often observed when performing updates and diffs using both the command line and subclipse.

What I've seen is that when the slowness does occur the Linux box doesn't have a lot of CPU utilization, in fact it's often near zero but I do see a lot of iowait, sometimes as much as 98%.

I'm not sure what else to do in terms of troubleshooting this. Is the problem related to the fact that I'm running svnserve -d manually?

Thanks for any help,

Christian Cabanero

Christian Cabanero
Senior Technical Program Manager
Amazon.com
cabanero@amazon.com
http://www.amazon.com <http://www.amazon.com>
Received on Wed Mar 15 10:30:27 2006