> https://issues.apache.org/jira/browse/CASSANDRA-1417

[snip, row cache saving only keys]

> Is this the intentional implementation?  Are there any reason not to
> just the entire row to disk to allow for faster startup?

Intentional (in the sense of "not a mistake"), but see:

   https://issues.apache.org/jira/browse/CASSANDRA-1625

The reason your start-up took a lot of time is that reading in the
values associated with the keys is entirely seek-bound (except in
certain edge cases). Eliminating the need for seek-bound I/O to
populate the row cache was the purpose of filing 1625.

In practice, you do have to consider the expected start-up time when
sizing your row cache.

-- 
/ Peter Schuller

Reply via email to