On Tue, Jun 24, 2014 at 11:04 AM, Stefan Sperling wrote:
> On Tue, Jun 24, 2014 at 12:50:52AM +0200, Stefan Fuhrmann wrote:
> > The serializer itself uses a single, auto-growing buffer.
> > It should show up as a temporary peak, though.
>
> There is a peak roughly above 200MB before the log messa
On Tue, Jun 24, 2014 at 12:50:52AM +0200, Stefan Fuhrmann wrote:
> The serializer itself uses a single, auto-growing buffer.
> It should show up as a temporary peak, though.
There is a peak roughly above 200MB before the log message
is printed. It then settles at 173MB for me.
> The current 100
On Mon, Jun 23, 2014 at 11:55 PM, Stefan Sperling wrote:
> 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.
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 runnin
4 matches
Mail list logo