[
https://issues.apache.org/jira/browse/CASSANDRA-8341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14229872#comment-14229872
]
Benedict commented on CASSANDRA-8341:
-------------------------------------
That is difficult, since we have stages that perform work that does not consume
CPU. The RPC stage (for thrift or cql) both spend the majority of their time
_waiting_ for the relevant work stage to complete. The proposed approaches
would count this as busy time. The read and write stages also can block on IO,
the former more often than the latter, but in either case we would count
erroneously.
> Expose time spent in each thread pool
> -------------------------------------
>
> Key: CASSANDRA-8341
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8341
> Project: Cassandra
> Issue Type: New Feature
> Components: Core
> Reporter: Chris Lohfink
> Priority: Minor
> Labels: metrics
> Attachments: 8341.patch, 8341v2.txt
>
>
> Can increment a counter with time spent in each queue. This can provide
> context on how much time is spent percentage wise in each stage.
> Additionally can be used with littles law in future if ever want to try to
> tune the size of the pools.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
