Karl Fogel wrote:
> Karl Fogel <kfogel_at_red-bean.com> writes:
>> "Peter Wemm" <peter_at_wemm.org> writes:
>>> Suppose you have a large svn repository and people who like inviting
>>> trouble. An example of 'large' in my case is the output (fsfs) of
>>> cvs2svn of the freebsd.org src repository. There are only 180K
>>> changes, but there are many thousands of branches and tags and copies.
>>> The namespace is quite large and convoluted.
>>>
>>> Running 'svn propget -R svn:author file:///path/to/repo' is a good
>>> way to find out how your machine handles running out of swap space...
>>> In my case, the svn process had reached *19GB* before something broke.
>> [...patch...]
>
> Peter, I've committed that patch in r30743. It seemed right. But your
> feedback is still important. If the patch doesn't solve the problem,
> then either more needs to be done, or something different needs to be
> done, or perhaps both.
Patch looks good here. You don't need a massive dataset to see that before
the patch memory usage grows, and afterward it doesn't. I trust Peter's
testing will confirm as much.
--
C. Michael Pilato <cmpilato_at_collab.net>
CollabNet <> www.collab.net <> Distributed Development On Demand
Received on 2008-04-22 07:37:11 CEST