On Thu, Jan 9, 2014 at 5:02 PM, Aaron Morton wrote:
> Row cache has been off heap for a while, and the key cache is still on
> heap.
>
Usage of the "off heap" row cache has enough associated heap consumption
that I feel compelled to mention that the name "off heap" is slightly
misleading. Certain
in 1.2 bloom filters and compression meta data were moved off heap. in 2.0
index samples were also taken off heap.
Row cache has been off heap for a while, and the key cache is still on heap.
Any other components you were interested in ?
The best reference will be the NEWS.txt file and the
Solely by the Cassandra version. Are you asking about a particular
component not mentioned above?
Not exactly. From version to version, the component of cassandra may reside
on heap or off heap, so is there a way to determine which component in the
cassandra version that may reside on heap or off
On Tue, Dec 31, 2013 at 7:35 AM, Jason Wee wrote:
>
> In Cassandra 1.2 and later, the Bloom filter and compression offset map
> that store this metadata reside off-heap, greatly increasing the capacity
> per node of data that Cassandra can handle efficiently. In Cassandra 2.0,
> the partition sum
Excerpts from
http://www.datastax.com/documentation/cassandra/2.0/webhelp/cassandra/operations/ops_tune_jvm_c.html
In Cassandra 1.2 and later, the Bloom filter and compression offset map
that store this metadata reside off-heap, greatly increasing the capacity
per node of data that Cassandra can h
