Re: Simultaneous svnserve requests lead to "Can't read from connection: Connection reset by peer"

Ryan Schmidt <subversion-2014_at_ryandesign.com> writes:

> Is there a limit on the number of simultaneous connections I can make
> from a single svn client to svnserve?

No, there is no rate limiting at all in 1.8 svnserve: it will attempt to
start threads/processes as fast as incomming connections arrive. This
can cause the server to run out of resources which may in turn cause
processes to get killed. However your test case of 10 simultaneous
exports isn't very big so I'd not expect a problem.

> The client and server are on a local network connected by 100mbit
> Ethernet. Both are 64-bit Intel Macs running OS X 10.9.2 with
> Subversion 1.8.8 installed using MacPorts. The server is started with
> a shell script containing:
>
> #!/bin/sh
> svnserve --daemon --foreground --read-only --log-file /dev/stdout --client-speed 100 --root "$(dirname "$0")"

You say you want it to be faster. If svnserve is the bottleneck then
using thread mode rather than fork mode and increasing the size of the
FSFS cache will make svnserve much faster, your network may well become
the bottleneck.

http://subversion.apache.org/docs/release-notes/1.7.html#server-performance-tuning
http://subversion.apache.org/docs/release-notes/1.8.html#fsfs-enhancements

-- 
Philip Martin | Subversion Committer
WANdisco // *Non-Stop Data*