You should be using the off heap row cache option. That way you avoid GC
overhead and the rows are stored in a compact serialized form that means you
get more cache entries in RAM. Trade off is slightly more CPU for
deserialization etc.
Adrian
On Sunday, September 11, 2011, aaron morton wrote:
>
If the row cache is enabled the read path will not use the sstables. Depending
on the workload I would then look at setting *low* memtable flush settings to
use as much memory as possible for the row cache. If the row is in the row
cache the read path will not look at SSTables.
Then set the ro
Hi, all.
I´m new at this and haven´t been able to install cassandra in debian
6. After uncompressing the tar and creating var/log and var/lib
directories, the command bin/cassandra -f results in message "exec:
357 -ea not found" preventing cassandra from run the process README
file says it is supp
Hi,
Can we configure some column-families (or keyspaces) in Cassandra to perform
as a pure in-memory cache?
The feature should let the memtables always be in-memory (never flushed to
the disk - sstables).
The memtable flush threshold settings of time/ memory/ operations can be set
to a max value
