[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 18:59:11 CEST

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

> The main problem I'm seeing right now is that checkouts take an
> extremely long time and always fail partway through, requiring a
> process like this: checkout, fail; update, fail; update, fail; update,
> complete. After that, one has the repository and further updates do
> not fail. However, even then an update which winds up pulling down
> only, say, 200 KB of changed data will take, on average, thirty
> minutes. The error on new checkouts is below:
> Error: REPORT request failed on '/<path edited>/!svn/vcc/default'
> Error: REPORT of '/<path edited>/!svn/vcc/default': 200 OK (http://foo
> <http://foo>)

You said a lot about how large your repository is, but very little
about how large your working copies are. Are you actually checking
out the entire repository? Most very large repositories are
structured such that you check out subsets of them for day to day
work, if you really need to check out 140000 files for each working
copy, that may have performance implications.

Also, FWIW, that totally useless error message from your checkouts
should at least be a less useless error message in Subversion 1.5. I
fixed that recently.

> Another problem is that I can no longer use dumps and loads now that
> we have >2GB revisions in the repository. Is there any way around this
> limitation?

Why not? Assuming you build with a suitable version of APR you should
be able to dump arbitrarily large repositories...


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Oct 6 19:00:47 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.