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

Scalability problem using svn_load_dirs.pl during

From: Mats Nilsson <mats.nilsson_at_xware.se>
Date: 2003-06-18 13:20:59 CEST

Hi.

I tried to use svn_load_dirs to archive some external stuff that we use.
Sadly svn ran out of memory in the process.

Granted, the machine that I use is not particularly powerful, and I've
seen many accounts on this list of more able machines running into the
wall.

When it processes the second version of the external library, it quite
quickly goes through the harvesting of information, and the first call
to svn:
        svn add -N --targets ....
But when it calls the next command (svn rm --targets ...), the svn grows
until all memory and swap is exhausted

I've searched issuezilla for scalability/performance issues, but nothing
that explicitly pertains to "svn rm".

Specifics:
Machine
        RH9.0, 256 Megs of memory, 512 Megs of swap, 750 MHz
Subversion
        0.24.1 (built from tarball)

In case anyone wants to try to reproduce:
I downloaded
        http://deuce.doc.wustl.edu/old_distribution/ACE-5.3.zip
        http://deuce.doc.wustl.edu/old_distribution/ACE-5.3.1.zip

And then unpacked into
        ~/tmp/ace-5.3 and
        ~/tmp/ace-5.3.1

mkdir -p ~/tmp/ace-5.3 ~/tmp/ace-5.3.1
cd ~/tmp/ace-5.3
unzip ~/ACE-5.3.zip
cd ~/tmp/ace-5.3.1
unzip ~/ACE-5.3.1.zip
cd ~/tmp
svnadmin create /usr/local/svn/repos
svn mkdir file:///usr/local/svn/repos/libs -m ""
svn mkdir file:///usr/local/svn/repos/libs/ACE -m ""
svn mkdir file:///usr/local/svn/repos/libs/ACE/trunk -m ""
svn mkdir file:///usr/local/svn/repos/libs/ACE/tags -m ""
perl ~/subversion/tools/client-side/svn_load_dirs.pl
file:///usr/local/libs/ACE trunk -t 'tags/@.*@' ace*

And then I accept all defaults.

The first version goes in nicely, and it has 6348 files in 248
directories. About 60Mb unpacked.

The second version has 4899 files in 230 directories. A few directories
have hundreds of files each.
The difference to the first version consists of a few directory and file
additions, roughly one hundred changed files in mostly one directory,
and files removed from two directory trees.

As stated above, during the second round, svn rm eats all my memory.

Is this related to other performance/scalability issues?

Mats

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jun 18 13:19:50 2003

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.