On Sat, Oct 22, 2005 at 03:12:51PM +0300, Marius Gedminas wrote:
> I keep bits of my home directory in a Subversion repository. It has 600
> revisions and occupies 250 megs of disk space. It uses bsddb. I kept
> it on a server running Subversion 1.1.4 from Debian sarge, and committed
> stuff to it from my laptop running Subversion 1.2.0 from Ubuntu breezy
> over svn+ssh.
...
> Then I decided to do 'svn up' in the
> root of the checkout on my laptop. Nothing happened for a while, but
> after a few minutes svnserve on the server side ate all available RAM
> and swap, and caused the kernel to invoke the OOM killer. The server
> has 512 megs of RAM and 2 gigs of swap!
>
> I thought those two big commits were causing a problem. I decided to
> use svnadmin dump and svndumpfilter. svnadmin dump dumped 5 revisions
> successfully and started eating all the memory while processing rev 6.
> I killed it. svnadmin verify acts likewise.
> I scp'ed the repository to my laptop, ran svnadmin recover for good
> measure, and retried svnadmin dump with Subversion 1.2.0. The same
> thing happened. svnadmin eats about 300 megs of RAM in 20 seconds, then
> I kill it.
This is now http://subversion.tigris.org/issues/show_bug.cgi?id=2430
Marius Gedminas
--
(define the-question (or (* 2 b) (not (* 2 b))))
Received on Tue Nov 1 13:31:13 2005