[
https://issues.apache.org/jira/browse/CASSANDRA-12027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Stupp resolved CASSANDRA-12027.
--------------------------------------
Resolution: Duplicate
> Provide metrics for thread pool heap and CPU usage
> --------------------------------------------------
>
> Key: CASSANDRA-12027
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12027
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Robert Stupp
> Assignee: Robert Stupp
> Priority: Minor
> Fix For: 3.x
>
>
> While working on some load tests and digging through the causes of certain
> things, it was very useful to know which thread pools actually consume how
> much heap and CPU.
> I already have some general implementation in place, but this assumes that
> the thread names stay constant. CASSANDRA-11966 is about to change this, so
> the general approach no longer works. Instead, measuring CPU and heap usage
> would need to be accumulated in SEPWorker for the actual (logical) thread
> pool.
> Purpose of this ticket is to provide the following metrics:
> * CPU and heap usage per statically named C* thread
> * CPU and heap usage per non-shared C* thread pool
> * CPU and heap usage per shared C* thread pool
> * CPU and heap usage for Netty thread pools
> This information would be exposed as "ordinary" metrics.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
