cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Burroughs (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-1966) Option to control how many items are read on cache load
Date Thu, 16 Jun 2011 18:25:48 GMT


Chris Burroughs commented on CASSANDRA-1966:

My view is that if you are using this it's because you have decided on a constraint like "Need
to be able to restart within t time units" and are choosing how many row keys to save based
on that, not as a function of total row cache capacity.  I don't mind working backwards from
a % configuration if there is a case when that makes more sense.  I don't think it's worth
the complication to support both.

> Option to control how many items are read on cache load
> -------------------------------------------------------
>                 Key: CASSANDRA-1966
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Chris Burroughs
>            Assignee: Chris Burroughs
>            Priority: Minor
>         Attachments: 1966-v1.txt
> CASSANDRA-1417 added an option to save the key and/or row cache keys which is cool. 
However, for a row large cache it can take a long time to read all of the rows.  For example
I have a 400,000 item row cache, and loading that on restart takes a little under an hour.
> In addition to configuring the size of the row cache, and how often it should be saved
to disk, I propose an option to control how many items are loaded on startup (or alternately
only saving n items out of the full row cache to begin with).

This message is automatically generated by JIRA.
For more information on JIRA, see:


View raw message