Re: memtable_threshold

2011-03-31 Thread ruslan usifov
Fo all who reply on this topic, thanks, for you patience and explanations

Re: memtable_threshold

2011-03-28 Thread Jonathan Ellis
It's closer to 8x than 2x for small values. Java objects simply use a lot more memory than you'd think, and it takes multiple objects to store a column. http://kohlerm.blogspot.com/2008/12/how-much-memory-is-used-by-my-java.html On Mon, Mar 28, 2011 at 4:15 PM, ruslan usifov wrote: > > > 2011/3/

Re: memtable_threshold

2011-03-28 Thread Narendra Sharma
Following shows how the size of memtable is updated: currentThroughput.addAndGet(cf.size()); The jconsole/JMX shows this and this doesn't account for the overhead of holding the data in in-memory data structures. The size of CF, SuperColumn and Column is calculated as following: Column Size: pub

Re: memtable_threshold

2011-03-28 Thread ruslan usifov
2011/3/29 Narendra Sharma > This is because the memtable threshold is not correct to the last byte. The > threshold basically account for column name, value and timestamp (or the > serialized column). It doesn't account for all the in-memory overhead for > maintaining the data and references etc.