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

Re: Svn update slow for a small repository

From: Ryan Schmidt <subversion-2006Q1_at_ryandesign.com>
Date: 2006-03-15 00:22:51 CET

On Mar 14, 2006, at 23:18, Cabanero, Christian wrote:

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

> 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'd also be interested to know more about this. We also experience
occasional iowait slowness sometimes up to a few minutes when
updating or committing a working copy. Our repository is served from
a Gentoo Linux machine through Apache 2.0.54. I thought the iowait
was due to the working copies, which in our scenario are also being
stored on the Linux server and accessed from desktop workstations
over Samba. But perhaps it's due to the server-side repository
operations?

The time needed will be proportional not to the size of the working
copy but to the number of directories, if I understand correctly.
Perhaps that applies in your case? I think it applies in ours... I
have a working copy which (without the .svn directories) is 71MB
large and contains (without the .svn directories) 1250 directories.

I would think allocating more memory to disk cache, or getting a
faster RAID, would help. We have a RAID, but apparently it's not good
enough. Or something.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Mar 15 00:24:06 2006

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.