cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Burroughs (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-6591) un-deprecate cache recentHitRate and expose in o.a.c.metrics
Date Fri, 29 May 2015 14:35:20 GMT

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

Chris Burroughs updated CASSANDRA-6591:
---------------------------------------
    Attachment: j6591-2.1-v4.txt

Misses removed.

> un-deprecate cache recentHitRate and expose in o.a.c.metrics
> ------------------------------------------------------------
>
>                 Key: CASSANDRA-6591
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6591
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Chris Burroughs
>            Assignee: Chris Burroughs
>            Priority: Minor
>         Attachments: j6591-1.2-v1.txt, j6591-1.2-v2.txt, j6591-1.2-v3.txt, j6591-2.1-v4.txt
>
>
> recentHitRate metrics were not added as part of CASSANDRA-4009 because there is not an
obvious way to do it with the Metrics library.  Instead hitRate was added as an all time measurement
since node restart.
> This does allow changes in cache rate (aka production performance problems)  to be detected.
 Ideally there would be 1/5/15 moving averages for the hit rate, but I'm not sure how to calculate
that.  Instead I propose updating recentHitRate on a fixed interval and exposing that as a
Gauge.



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

Mime
View raw message