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

Re: svn+ssh <-> svnserve <= speed concerns

From: John Peacock <john.peacock_at_havurah-software.org>
Date: Tue, 29 Jul 2008 07:05:50 -0400

Marko Kning wrote:
> Well, so this slow-down is still present, even if I use svnserve? Of
> course... I do use svn+ssh...

As I said, when you use svn+ssh, you are not running svnserve as a server
process, but rather once per connection. This mode of operation is actually
much more like using file:// protocol, just remotely.

> So, the only way to make it significantly faster is actually to avoid ssh
> at all. Is that what you want to say?

It depends on what you are trying to really accomplish:

In terms of performance, svnserve (as a server) has lower overhead (because the
protocol is simpler) but Apache/DAV using serf on the client can be faster
overall (because it is more efficient in the reuse of connections).

On the other hand, svnserve has very little in the way of support for fancy
authentication, whereas in Apache the skies the limit.

In terms of security, svn+ssh is probably most secure, since the traffic is
encrypted and you can (as you have already done) require the use of client
certificates to access the repo which is additionally owned by a single user.
On the other hand, if what you are most concerned with is over-the-wire
security, you can accomplish the same thing with https:// and client certificates.

It all depends on what you want. If you want high performance *and* high
security, you should probably be using Apache with SSL certificates (client and


To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-07-29 13:06:19 CEST

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.