Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Tue, 26 Jul 2011 18:45:10 +0000 (UTC)
From: "Jonathan Ellis (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: 
 <453172633.8918.1311705910614.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: <28973927.294401294778446558.JavaMail.jira@thor>
Subject: [jira] [Updated] (CASSANDRA-1966) Option to control how many items
 are read on cache load
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CASSANDRA-1966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Ellis updated CASSANDRA-1966:
--------------------------------------

    Reviewer: jbellis

> Option to control how many items are read on cache load
> -------------------------------------------------------
>
>                 Key: CASSANDRA-1966
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1966
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Chris Burroughs
>            Assignee: Chris Burroughs
>            Priority: Minor
>             Fix For: 1.0
>
>         Attachments: 1966-v1.txt, 1966-v2.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: http://www.atlassian.com/software/jira