Re: Disruptor memory management

2016-11-10 Thread 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

Disruptor memory management

2016-11-09 Thread 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