Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Message-ID: <12456358.303761294798967087.JavaMail.jira@thor>
Date: Tue, 11 Jan 2011 21:22:47 -0500 (EST)
From: "Chris Burroughs (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Subject: [jira] Commented: (CASSANDRA-1966) Option to control how many items
 are read on cache load
In-Reply-To: <28973927.294401294778446558.JavaMail.jira@thor>
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:comment-tabpanel&focusedCommentId=12980513#action_12980513 ] 

Chris Burroughs commented on CASSANDRA-1966:
--------------------------------------------

I take this to mean that ConcurrentLinkedHashMap does not provide the ability to iterate -- in even an approximation of -- "least likely to be evicted next" order.

> 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
>
> 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.
-
You can reply to this email to add a comment to the issue online.