Re: Subversion on a large repository

On Friday 15 February 2008, Vishnu Venkatesan wrote:
> Hi Marc,
> Thanks for your response. By concurrent I meant 100-200 commits per
> second which could be the peak load on the repository. I did some simple
> tests and having concurrency issues. I hosted a repository on a NFS and
> had two svnserve daemons running in two different machines. When two
> concurrent commits were issued using the two different svnserve daemons,
> the repository is in a weird state and doesnt allow any more commits
> with an error as checksum mismatch.

100-200 commits PER SECOND ? You must have more than hundred thousand ACTIVE
developers or are firing at the repository with several scripts to reach that
load, I guess.

Anyway, as other have already said NFS is the biggest problem. It lacks file
locking (which might be reason for your repository corruption).

I have never heard of someone running two daemons on the same repository and I
don't quite see how this would solve your problem as the biggest bottleneck
is IO, not CPU (and having IO over network is making matters worse here: you
will fill your network interfaces twice as fast). Having one daemon on a
decent hardware with a good RAID system might be a better idea.

Bye,
        Marc

-- 
Marc Haisenko
Comdasys AG
Rüdesheimer Str. 7
80686 München
Germany
Tel.: +49 (0)89 548 433 321
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org