[
https://issues.apache.org/jira/browse/CASSANDRA-19671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17851829#comment-17851829
]
Arun Ganesh edited comment on CASSANDRA-19671 at 6/3/24 10:29 PM:
------------------------------------------------------------------
Yes, the ratio is calculated like this,
{code:java}
statsTable.localReadWriteRatio = statsTable.localWriteCount > 0 ?
statsTable.localReadCount / (double) statsTable.localWriteCount : 0;
{code}
Since it is already present, maybe you can update the ticket.
was (Author: JIRAUSER303038):
Yes, the ratio is calculated like this,
{code:java}
statsTable.localReadWriteRatio = statsTable.localWriteCount > 0 ?
statsTable.localReadCount / (double) statsTable.localWriteCount : 0;
{code}
> Nodetool tabestats: add keyspace space used and table r/w ratio
> ---------------------------------------------------------------
>
> Key: CASSANDRA-19671
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19671
> Project: Cassandra
> Issue Type: Improvement
> Components: Tool/nodetool
> Reporter: Brad Schoening
> Assignee: Arun Ganesh
> Priority: Low
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Nodetool tabestats reports the space used live and total per table, but not
> for the entire keyspace. This would be useful information.
> Also, in the table level stats, it would be useful to have the read/write
> ratio. This metric is important in choosing compaction strategies such as
> LCS.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
