about the deep clone operation in the cassadra source code

When I read the cassandra code, there are too many deep clone operation. Is there any risk of OutOfMemoryException? When flushing the memtable to disk, there is a deep clone, and when the disk is slow down, this will lead to a severe OOM. Am I right? Thanks. 2012-02-21 zhangcheng

about the compaction and read performance

in the most recent sstable, by this, I think the read and write performace will be better. Thanks. 2012-02-17 zhangcheng

Re: Re: Key cache hit rate issue

all in the most recent sstable, by this, I think the read performace will be better. 2012-02-17 zhangcheng 发件人： Jonathan Ellis 发送时间： 2012-02-17 10:13:20 收件人： user 抄送： 主题： Re: Key cache hit rate issue On Thu, Feb 16, 2012 at 3:52 PM, Eran Chinthaka Withana wrote: > Thanks

Re: Re: Key cache hit rate issue

Thanks, Jonathan. I got it. 2012-02-17 zhangcheng 发件人： Jonathan Ellis 发送时间： 2012-02-17 10:15:05 收件人： user 抄送： 主题： Re: Key cache hit rate issue Look for this code in SSTableReader.getPosition: Pair unifiedKey = new Pair(descriptor, decoratedKey); Long

Re: Re: Key cache hit rate issue

according to the read process, the key of the keycache should be the row key. 2012-02-17 zhangcheng 发件人： Todd Burruss 发送时间： 2012-02-17 06:23:47 收件人： user@cassandra.apache.org 抄送： 主题： Re: Key cache hit rate issue jonathan, you said the key to the cache is key + sstable? looking

Re: keycache persisted to disk ?

I think the keycaches and rowcahches are bothe persisted to disk when shutdown, and restored from disk when restart, then improve the performance. 2012-02-13 zhangcheng 发件人： Franc Carter 发送时间： 2012-02-13 13:53:56 收件人： user 抄送： 主题： keycache persisted to disk ? Hi, I am testing