[
https://issues.apache.org/jira/browse/CASSANDRA-8341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14230164#comment-14230164
]
Chris Lohfink commented on CASSANDRA-8341:
------------------------------------------
I'll write up something in a little bit, but a scheduled task to walk the
threads and capture the User time from the ThreadMXBean could give a good
picture of which thread pools are burning cpu (including cpu burnt waiting).
Can capture it from the SEPWorker when changing assigned executors. A problem
is (thanks [~benedict]) in the maybeExecuteImmediately when not adding the
task, that would need to be wrapped in an expensive call which adds latency to
read/writes.
> 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)
