"Gerald Richter" <richter@ecos.de> writes:
> >
> > Gerald, could memory usage be what is causing your check-out to fail?
> > I can easily drive my machine (512M RAM, 1G swap) first into swap and
> > then beyond its swap limit using a repository with a few hundred files
> > in one directory. When the Linux OOM killer kills the Apache httpd
> > process I see a message in the syslog but not in the Apache log.
> >
>
> Yes, that is it!!
>
> While doing the PROPFIND for the directory with 350 file, the Apache process
> grows to over 220MB and then is killed by the Linux OOM killer (my test
> machine has only 128KB of real memory). When I run a filesystem checkout,
> the svn command never grows over 14MB, so it seems a issue of
> mod_dav/mod_dav_svn?
>
> What is mod_dav doing that it needs 750KB per file for a PROPFIND? That
> really seems very very much?
>
> I like svn very much and every day I use it and discover new features I like
> it even more, but this seems to be a real show stopper...
You can work around the problem by checking-out revision zero and
then updating the working copy
% svn co -r 0 -d wc http://host/repo
% svn up wc
These commands use much less memory in the server process (about
twenty megabytes instead of two or three hundred in my tests.)
--
Philip
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jun 5 17:12:18 2002