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

Re: svnsync crashes on a huge commit

From: Stefan Fuhrmann <stefan.fuhrmann_at_wandisco.com>
Date: Thu, 18 Jul 2013 17:32:25 +0200

On Thu, Jul 18, 2013 at 4:08 PM, Anatoly Zapadinsky <zapadinsky_at_gmail.com>wrote:

> >> > Does the memory usage already build up while transmitting the
> >> > data (i.e. while the dots are being shown) or mainly during the
> >> > commit stage, i.e. the during short delay after the last dot and
> >> > the "Committed revision xyz" message?
> >>
> >> On transmitting data stage. During the commit almost no additional
> >> memory is allocated.
> >
> > So, it depends on the number of changes in a revision and / or
> > combined size of the changed nodes. Could you try running a
> > local replication, i.e. from file:// to file:// or svn:// to file:// ?
> > That way, we could rule out peculiarities of http and the serf lib.
> >
> I've tried to mirror the local chromium mirror using file:// protocol
> and it works fine, less than 40Mb was allocated.

That's excellent.

> I can't try svn://
> protocol I have no permission to access chromium project and we have
> no such server at work. If you will not be able to reproduce it on
> windows I can request read only permission to chromium project...

You may simply start "svnserve -Tdr /path/to/repo_parent --foreground"
and then svn://localhost/your_repo should be available.

-- Stefan^2.
Received on 2013-07-18 17:33:05 CEST

This is an archived mail posted to the Subversion Dev mailing list.