Re: svn commit: r982355 - /subversion/branches/performance/subversion/svnserve/main.c
From: Blair Zajac <blair_at_orcaware.com>
Date: Tue, 9 Nov 2010 19:42:25 -0800
On Aug 4, 2010, at 11:43 AM, stefan2_at_apache.org wrote:
> Author: stefan2
Some questions on this:
Do we not need this in mod_dav_svn because we assume that Apache exits child processes after N HTTP requests?
What about for Windows Apache servers, where they only have a threading server model, should this be enabled? Or would it be too hard to have only svn pools use this
We have a custom, multithreaded Ice Subversion server that can run for months at a time. It only serves full texts to clients and it doesn't expose any diff methods. I've seen slow growth over time, but we also have an internal LRU cache for svn_repos_t, svn_fs_t, svn_fs_root_t, so it's hard to tell what's allocating memory. I guess we should do that in this process just to be safe?
It looks like every command line tool we have does this:
./subversion/svnadmin/main.c:1578: apr_allocator_max_free_set(allocator, SVN_ALLOCATOR_RECOMMENDED_MAX_FREE);
Any reason we just don't make this part of svn_cmdline_init()?
This is an archived mail posted to the Subversion Dev mailing list.