Chris Freeze <cfreeze@cfreeze.com> writes:
> I'm working on a fairly large dump file of a repository (6gigs) that
> has a huge (about 400meg) vendor import on a particular commit
> revision. svndumpfilter dies on processing this commit from what looks
> like a sbrk call exhausting available memory. I'm seeing this on
> win32 and linux with the 1.0 release of subversion. Looks like
> svndumpfilter is putting a lot of memory pressure when a revision is
> extremely large. The repository itself is not terribly complex, but
> does have a significant amount of branching and merging in other areas
> (not in dealing with the directory of the vendor import that is giving
> svndumpfilter problems).
Are you sure that the memory usage is related to the size of the
revision, and not the number of dropped paths or dropped revisions or
something else? Also, have you tried using svndumpfilter from the
Subversion /trunk HEAD? I've made a few memory-related enhancements
there in recent weeks.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Mar 18 03:26:09 2004