[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

memory use of svn log -v with long changed paths lists

From: Stefan Sperling <stsp_at_elego.de>
Date: Mon, 23 Jun 2014 23:55:05 +0200

I'm still seeing 180MB of memory used by svn log -v with ruby's r11708
over ra_local with fsfs7-unpacked (120MB with fsfs6-unpacked).
The total output generated by svn log is only 5.5MB in size.
That seems somewhat disproportionate.

Of course, I'm happy that this invocation of svn log isn't running
out of memory anymore on my machine, as it did before r1604188!
So that's a huge step forward but I suppose we can still do better.

It seems caching is partly responsible for the memory growth.
I'm seeing huge jumps during svn_cache__set() calls, though we might
still be missing some scratch pools or iterpools to keep memory
usage low.

Does anyone know what can be done about this?
Received on 2014-06-23 23:55:36 CEST

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.