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

Re: Is my implementation too large for SVN?

From: Garrett Rooney <rooneg_at_electricjellyfish.net>
Date: 2006-10-06 20:14:58 CEST

On 10/6/06, John Thile <gilrain@gmail.com> wrote:

> > Why not? Assuming you build with a suitable version of APR you should
> > be able to dump arbitrarily large repositories...
> I am able to dump the repository just fine. However, when I try to
> load the resulting dumpfile, I get a "file size limit exceeded" error.
> I should have mentioned this only happens at a client site. Hmm,
> perhaps they simply built SVN the wrong way, then? I'll pass the APR
> tip along to them, thanks.

Note that the ideal situation for large file support in svn is using a
recent build of APR from the 1.2.x series of releases. 0.9.x is hit
or miss.

> One follow-up question: someone else mentioned they saw the
> large-checkout errors disappear when they switched to svnserve. I've
> always gotten the impression that the Apache implementation is the
> preferred method of running SVN. Is svnserve more stable or better
> able to scale with large repositories? I've really enjoyed the robust
> authentication and permissions of the Apache implementation, but I
> would consider switching if it were agreed that svnserve was faster or
> more stable.

Neither is "preferred", they both have their advantages. The protocol
used with svnserve is indeed faster in many cases, but the Apache
based server is more flexible in many ways and provides some
capabilities you can't get with svnserve today. It also works over
http and thus you often have fewer firewall problems with it than
you'd get with svnserve and its custom protocol.


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Oct 6 20:15:42 2006

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.