Mailing-List: contact cassandra-commits-help@incubator.apache.org;
 run by ezmlm
Precedence: bulk
Reply-To: cassandra-dev@incubator.apache.org
Message-ID: <462970136.335781266422007948.JavaMail.jira@brutus.apache.org>
Date: Wed, 17 Feb 2010 15:53:27 +0000 (UTC)
From: "Jonathan Ellis (JIRA)" <jira@apache.org>
To: cassandra-commits@incubator.apache.org
Subject: [jira] Commented: (CASSANDRA-801) The Key Cache should be
 configurable by absolute numbers
In-Reply-To: <554147736.315411266353008050.JavaMail.jira@brutus.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CASSANDRA-801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12834811#action_12834811 ] 

Jonathan Ellis commented on CASSANDRA-801:
------------------------------------------

i don't think this splits up the keys cached among the different sstables the way JMXAggregating cache does?  that should be consistent one way or the other.

> The Key Cache should be configurable by absolute numbers
> --------------------------------------------------------
>
>                 Key: CASSANDRA-801
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-801
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 0.5, 0.6, 0.7
>            Reporter: Ryan King
>            Assignee: Stu Hood
>             Fix For: 0.6, 0.7
>
>         Attachments: 0001-Convert-KeysCachedFraction-to-KeysCached.patch, 0002-Update-config-values.patch, 0003-Sane-defaults.patch
>
>
> Just like the row cache, the key cache should be configurable by absolute numbers (not just a fraction). It would be nice to configure it by either memory size or entries (like the row cache).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.