On 11/8/2010 8:54 PM, Paul Burba wrote:
> On Mon, Nov 8, 2010 at 8:28 PM, Chris Tashjian<ctash_at_thepond.com> wrote:
>> Paul - 1 more question. What happens when you run additional blame -g
>> commands? Does the memory usage keep growing until it runs out of memory or
>> will it cap itself at some point? In my tests it seems like memory wasn't
>> getting released very often. Granted, memory usage spun up so fast, I'm not
>> positive that it really had much of a chance for that to happen.
> Chris,
>
> I was describing *peak* memory use. The actual working set memory
> drops from 71 MB to 7 MB once the blame -g is processed in my example.
> Not sure how familiar you are with APR pools, but all the pools that
> get allocated to process the request should be destroyed (freed) when
> the server is done. If memory use is growing slowly after each blame
> -g, then that isn't happening and we have a separate bug. I just did
> a little ad hoc testing and there doesn't appear to be a problem.
> After several blame -g hits, the peak working set for my svnserve.exe
> process always returns to around 7 MB:
>
> 7464 K
> 7652 K
> 7500 K
> 7596 K
>
> If you discover anything contrary to this please let us know on the dev list.
I just restarted our svn server and ran blame -g against a file. No one
else is hitting the server right now and after 5 minutes mem usage is at
681,208K and the peak was 681,316K. (taskmgr screenshot:
http://img215.imageshack.us/img215/2060/svnserve.jpg)
Received on 2010-11-09 03:09:56 CET
