Our experience shows that write load (memtables) impacts ParNew GC most. More
writes, more frequent ParNew GC. Time of ParNew GC depends on how many writes
was made during cycle between ParNew GC's and size of NEW_HEAP (young gen).
Basicly ParNew GC itself takes longer when more objects have to
Thanks Aaron for the insight.
One quick question:
>The buffers are not pre allocated, but once they are allocated they are
>not returned. So it's only an issue if have lots of clients connecting
>and reading a lot of data.
So to understand you correctly, the buffer is allocated per client
connect
> *thrift_framed_transport_size_in_mb & thrift_max_message_length_in_mb*
This control the max size of a bugger allocated by thrift when processing
requests / responses. The buffers are not pre allocated, but once they are
allocated they are not returned. So it's only an issue if have lots of clie
