[
https://issues.apache.org/jira/browse/CASSANDRA-8341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14219374#comment-14219374
]
Chris Lohfink commented on CASSANDRA-8341:
------------------------------------------
yep understandable. Id like this if possible though so let me know if theres
anything I can do. A lot of the metrics library work happens after the task is
complete, in cases like read/write's they send back to a request response stage
so at least the post task work shouldn't affect the read/write latency until
the thread pool is saturated. I am not really sure if I know anything I can do
to counter the ~100ns-1us overhead though - any ideas?
> 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)
