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

Re: various questions related to repo size

From: <mixtim_at_acm.org>
Date: 2003-01-30 15:13:18 CET

Ben Collins-Sussman wrote:
 Jani Monoses jani@iv.ro writes:
2) The repository seemed to grow while the WS was updating.About
300M for each WS.Why should the repo care about an update and use up
so much space?It is in log.XXXXXXXX files which according to a mail
from Brane dated Jan 13th are required.The more clients the more the
repo grows? Does it keep some sort of repository for each client
separately?I don't think so because if one deletes a WS the repo
shouldn't care but the extra hundreds on megs would stay there.
 'svn up' creates a temporary mirror of the working copy in the
 repository, compares it to the HEAD tree to perform a tree delta, then
 removes the temporary mirror.
 Thus even 'svn up' requires Berkeley DB to temporarily write new
 data. What you're witnessing is BDB logging all of these writes.
 Luckily, you can use 'db_archive' to throw away old logfiles. It's
 all documented in the subversion book.

So if I follow you correctly then what your saying is that if you have a
500MB working copy and 10 people in your group all do an svn update then
you've just added 5GB worth of log files to your hard drive?

I'd classify that as a scalability issue as well.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 14 02:25:18 2006

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.