Because for small columns the Java "container" objects are larger than
the actual column data.
On Tue, Sep 13, 2011 at 9:38 AM, Radim Kolar wrote:
>> flush of Memtable-idx_graphable@915643571
> (4671498/96780112 serialized/live bytes, 59891 ops)
> can somebody explain why difference between live
flush of Memtable-idx_graphable@915643571*(4671498/96780112
serialized/live bytes, 59891 ops)
can somebody explain why difference between live and serialized is so
big? Serialized bytes are actual bytes written to sstable?
*
Thanks Jonathan !
memtable_total_space_in_mb is the threshold that is reached.
Kind regards,
Sorin
On Mon, Sep 12, 2011 at 3:16 PM, Jonathan Ellis wrote:
> see memtable_total_space_in_mb at
> http://thelastpickle.com/2011/05/04/How-are-Memtables-measured/
>
> On Mon, Sep 12, 2011 at 6:55 AM,
see memtable_total_space_in_mb at
http://thelastpickle.com/2011/05/04/How-are-Memtables-measured/
On Mon, Sep 12, 2011 at 6:55 AM, Sorin Julean wrote:
> Hi,
>
> I've checked the memtable flush (cassandra 0.8.4) and it seams to me it
> hapens sooner then the threshold is reached.
>
> Here's the
ct: Re: Memtable flush thresholds - what am I missing?
See http://thelastpickle.com/2011/05/04/How-are-Memtables-measured/,
specifically the section on memtable_total_space_in_mb
On Thu, Aug 18, 2011 at 2:43 PM, Dan Hendry
wrote:
> I am in the process of trying to tune the memtable flush thresho
See http://thelastpickle.com/2011/05/04/How-are-Memtables-measured/,
specifically the section on memtable_total_space_in_mb
On Thu, Aug 18, 2011 at 2:43 PM, Dan Hendry wrote:
> I am in the process of trying to tune the memtable flush thresholds for a
> particular column family (super column famil
