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

Re: initial setup one huge changeset or in pieces

From: gmu 2k6 <gmu2006_at_gmail.com>
Date: 2006-07-15 18:57:35 CEST

On 7/15/06, Ryan Schmidt <subversion-2006c@ryandesign.com> wrote:
>
> On Jul 15, 2006, at 18:04, gmu 2k6 wrote:
>
> > is there any performance impact whether I try to import an existing
> > tree in one step by import or add/commit or if I do it in some
> > well-defined steps? fsfs will be the backend.
> > btw, while trying to import a >5GiB tree with many C/Java sources and
> > a lot of binary resources svnserve (started via xinetd) just stopped
> > and refused any connections (according to the error message on the
> > client side). right now I'm trying to do it by adding and committing.
> > is there anyway to get logs from svnserve?
>
> I don't think there are any logs from svnserve.
>
> Commits of > 2 GiB are supported if you use APR 1.2.x or greater.
> They are not possible with APR 0.9.x for example. Check what version
> of APR you're using.

I've used Debian 2.0.x APR while building SVN-1.3.2. What's the reason for
bundling 0.9.x with Subversion?

> I have read recently on this list that there can be a performance
> problem if you have a very large commit and then try to do something
> with that revision, such as look at a log for it (IIRC). If these are
> separate projects you're importing, you'd do better to import them in
> separate commits.

actually this would be the initial revision/changeset so you can't do
any log on it,
only with newer csets against the first revision.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Jul 15 18:58:53 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.