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

memory problems w/ mod_dav_svn?

From: Vincent Rivellino <vince_at_cuz.cx>
Date: Mon, 4 Aug 2008 12:16:10 -0400 (EDT)

Has anyone run into memory problems using mod_dav_svn w/ rather large
repositories?

I recently migrated our repositories to 1.5.1 and moved them from svn+ssh
to mod_dav_svn via https.

After one of my users checked out the largest project (about 800MB
checkout), our SVN server ran out of memory and the kernel had to kill
processes. I was able to recreate the problem by checking out the same
repo again and watching top on the server. This is a snippet of top
*after* the checkout completed:

   PID USER PR VIRT RES SHR %CPU %MEM TIME+ CODE DATA nFLT
nDRT COMMAND
 19167 apache 16 1655m 1.4g 2664 0 36.0 3:59.93 288 1.4g 0
0 httpd

In this case the system didn't run out of memory, but the httpd process
that served my checkout didn't seem to give back the memory it used during
the checkout process.

I really don't want to have to move back to svn+ssh as the transport,
because I like not having to give system accounts to the engineering
staff. We're also using mod_authz_svn because we need to restrict
repository access to outside consultants.

Can anyone offer any insight?

Thanks,
Vince

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-08-04 18:16:34 CEST

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