On Thu, May 21, 2009 at 05:50:49AM -0700, webpost_at_tigris.org wrote:
> Hi,
>
> > But still, adding a large number of files should be done using
> > svn import. What does 1.6 do if you use svn import instead of svn add?
>
> svn import works fine and stays low on memory consumption as well.
Thanks for the information.
> > I would suspect issue #1964,
> > http://subversion.tigris.org/issues/show_bug.cgi?id=1964
>
> Actually I do not think that this is sufficiently covered by issue
> 1964 as source branches the size of boost worked with 1.5.4 or lower
> 1.5 versions but do not work anymore with 1.6.x versions. So something
> has gotten really worde here. To me it seems that after each sending
> statement of the commit 1MB is allocated, which is death if you have
> more then 2000 files to commit.
>
> Nevertheless I really think this is annoying because if i make changes
> over a lot of files I'm always in the danger of running low on memory.
> And Yes it has happened that i commit 2000+ files.
>
> Please inform me if I should add my concerns to the issue #1964
We've gotten more reports on this matter. It really looks like memory
usage during commit has increased in 1.6, up to the point of breaking
large commits of merge results. This cannot be worked around with svn
import, so issue #1964 has been given higher priority now.
I hope this problem will somehow be fixed by 1.7 at least, and possibly
also in a 1.6.x point release. You can add your email address to the
Cc list of issue #1964 if you want to be informed when progress is made.
If no one else beats me to it, I will try to find some time for looking
at this more deeply as soon as possible, hopefully during the next month
the latest.
In the meantime, you'll either have to use 1.5 to make large commits,
or split up your merges into smaller chunks and commit the chunks
individually. Obviously neither workaround is really acceptable,
so we will have to provide a fix for this.
Thanks for your patience,
Stefan
Received on 2009-05-21 16:27:48 CEST