Re: Big memory use after update

On Fri, 28 Nov 2003 11:10:45 +0100, Roland Schwingel
<Roland.Schwingel@onevision.de> wrote:

>
>Hi...
>
>> Memory for the Apache process went straight up from 270 MB to ~900 MB!
>> And it didn't go down after the update and the rest of operations
>> (delete the files, commit, status, etc.). I've had to manually restart
>> Apache.
>>
>> Is that normal/expected?
>I am making similar observations since 0.29.0 (ok, maybe I haven't checked
>that earlier).
>I made a test last weekend. Normally I do have eg. php also in apache and I
>did
>not knew whether this might be related to this additional software or not.
>
>I removed anything from apache except svn and restarted apache to get back
>memory
>on my server. On weekend there where 6 complete checkouts of my repos from
>one
>certain client, and just 2 very small checkins (everything script
>controlled).
>Besides that no svn usage in the network.
>
>On monday morning I made similiar observations. Memory grew to ~800MB. And
>I
>needed 4 apachectl stop calls to get rid of all running httpds. After one
>apachectl start everything is fine for me again. But just for about 24
>hours.
>
>I do this stopping and starting apache every day since about 3 weeks. As of
>the fact
>I couldn't find any reports for this problem on the list I was thinking it
>is a home made
>problem. But now, it does not seem so...
>
>Affected environment for my weekend thing:
>server: apache 2.0.48, bdb 4.0.14, svn 0.33.1, linux 2.4.20
>client: apache 2.0.48 (without svn), svn 0.33.0, linux 2.4.20
>
>So it appears there might be some leaking...

Subversion 0.31
Apache 2.0.47
Berkeley-db 2.0.14
kernel 2.4.19 SMP
SuSe 8.2

This system is a single-user archive. I've been using it for some
medium-sized projects (<3000 files) and I notice that some of my seven
httpd processes balloon up to 14Mb RSS as reported by top after remote
svn operations involving a commit of most of the files.

It's hard to tell which part of the operation causes the memory use. I
can see httpd processes consuming cpu without apparently growing in
size.

This looks scary, huh? However while the processes sometimes get
bigger than 14Mb (I've seen up to 25) they fall back to 14 almost
immediately. Even more interestingly, after a ~24 hours they're all
back to 8000-3000.

I'm not an Apache expert but this looks like Apache keeping buffers on
the grounds you might need them again rather than a leak.

I tried MaxMemFree as suggested by Sander in
<1070017333.3749.173.camel@localhost.localdomain> at the global level
but it seemed to make no difference.

Any Apache experts know for sure what's going on here? Would the same
thing happen in W32?

--
best,
geoff
regrettably the email address above will bounce
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org