It's a design flaw in how mod_dav walks the tree - basically, it needs to
store the response in a separate pool and use an iterative subpool for each
file that it looks up. Right now, we can't use an iterative subpool
approach because the response is stored in the same pool as the file
lookups. So, the memory growth is linear based on how many files are in a
directory.
It's somewhere on my todo list, but if someone else wants to tackle it,
please be my guest. =) -- justin
--On Thursday, October 10, 2002 12:20:29 -0400 Jeff Stuart
<jstuart@computer-city.net> wrote:
> OUCH!!!! NO WONDER my one check out failed! Does anyone know why that
> much memory is getting used? IE I assume that it's a bug yes? (I hope.
> :))
>
> On Thu, 2002-10-10 at 11:17, Philip Martin wrote:
>> The last time I looked, a PROPFIND on a directory with 800 hundred
>> elements used over 200MB of RAM, and the memory use scaled worse than
>> linearly with the number of elements :-(
>
> --
> Jeff Stuart <jstuart@computer-city.net>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Oct 10 20:18:54 2002