Re: Disruptor memory management

[Remko Popma]

Yes, this is the default. 

You can can reduce the ring buffer size in the configuration to reduce memory 
consumption. 

An alternative is to switch off garbage-free mode by setting system property 
"log4j2.enable.threadlocals" to false. This will cause Log4j to cache less and 
allocate temporary objects on the fly. 

Sent from my iPhone

> On 10 Nov 2016, at 16:55, David Leonhartsberger  wrote:
> 
> Hi,
> 
> I just checked one heap dump and I see that all array elements in the
> Disruptor keep track of a StringBuilder with size of 128.
> I currently use a capacity of 56k so this means I retain around 30MB of
> heap in idle situations.
> 
> Is this the default behaviour of log4j or am I doing something wrong?
> 
> Br,
> David

-
To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-user-h...@logging.apache.org

Disruptor memory management

[David Leonhartsberger]

Hi,

I just checked one heap dump and I see that all array elements in the
Disruptor keep track of a StringBuilder with size of 128.
I currently use a capacity of 56k so this means I retain around 30MB of
heap in idle situations.

Is this the default behaviour of log4j or am I doing something wrong?

Br,
David