Vishnu Venkatesan <vishnu.venkatesan_at_oracle.com> wrote on 02/15/2008
11:34:18 AM:
> 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.
>
> Steps:
> 1. Create a simple svn repo on a network filesystem using FSFS
> 2. Start svnserve daemon on two different machines which has access to
> the network file system repository
> 3. Checkout files from the svn repository using the two different
> svnserve daemons running in different machines.
> 4. commit files simultaneously using the two svnserve daemons
> (surprisingly both the commits resulted in the same revision number)
> 5. When I do update on the checkouts one of them is in an inconsistent
> state and doesnt allow further commits.
>
> Is running two svnserve daemons on a single repository is supported ? I
> am doing this just to make sure that in case if having one svnserve
> daemon's doesn't scale for 100-200 concurrent users per second I can
> have two machines handling the commits.
NFS performance is going to be your real killer. Subversion is usually
more I/O intensive than CPU intensive. Using multiple svnserve
processes on different machines on the same repo is probably not
recommended. (We use apache, so I can't comment directly on svnserve)
100-200 commits per second seems quite high. We normally do not
go above 10-20 per second with our 2000 users...
Kevin R.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-02-15 23:09:31 CET