On Nov 1, 2006, at 12:59, Talley, Brooks wrote:
> I've been using Subversion for a couple of years now on the same
> project, and it really seems to me that commits are getting slower and
> slower. The current version of the repository is on revision 900
> or so,
> and holds about 5,000 files totalling about 1GB. Maybe 200 of those
> files see regular commits (they're the source code; the rest of the
> repository is graphics and other resources).
>
> These days, commiting a 5k source file via svn:// is taking between
> 60-120 seconds. Not the end of the world, but I sure remember it
> being
> quicker.
>
> Are there any best-practice repository maintenance activities that we
> should be doing? The repository runs FSFS, and is on a fairly beefy
> server. During checkins, both CPU and disk on the server seem
> bored, so
> I'm not sure what the delay is.
>
> Any ideas?
Do you have a pre- or post-commit hook doing something time-consuming?
Does Subversion need entropy while committing? (I don't remember.) If
so, is your APR compiled to use /dev/random, and is /dev/random slow
on your OS? You can test it: while committing, try to read from /dev/
random and see if it takes a long time. If so, you may want to
recompile APR to use /dev/urandom which is always fast and still
sufficiently random for Subversion's purposes.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Nov 1 20:41:46 2006