You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Chris Burroughs (JIRA)" <ji...@apache.org> on 2015/07/22 22:35:04 UTC

[jira] [Assigned] (CASSANDRA-9872) only check KeyCache when it is enabled

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

Chris Burroughs reassigned CASSANDRA-9872:
------------------------------------------

    Assignee: Chris Burroughs

> only check KeyCache when it is enabled
> --------------------------------------
>
>                 Key: CASSANDRA-9872
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9872
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Chris Burroughs
>            Assignee: Chris Burroughs
>              Labels: cache, metrics
>
> If the KeyCache exists (because at least one column family is using it) we currenlty check the key cache even for requests to column families where the key cache is disabled.  I think it would be better to only check the cache if entries *could* be there.
>  * This will align the key cache with how the row cache behaves.
>  * This makes the key cache metrics much more useful.  For example, 'requests' becomes 'requests to things that could be in the key cache' and not just 'total requests'.
>  * This migh be a micro-optimization saving a few metric update.
> only count 'hit-able' requests as key cache misses



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)