tjiuming opened a new issue, #18038: URL: https://github.com/apache/pulsar/issues/18038
### Motivation Introduce the metrics for thread CPU usage which can help Pulsar maintainers to detect performance issues related to parts of threads that run with high CPU usage, especially the IO thread. This part is also the missing part of Apache Pulsar. The thread pool and thread CPU usage are very useful for troubleshooting performance issues like publishing latency spikes. And we can also adjust the ThreadPool according to the metrics, increase the number of threads of a certain type, or decrease. It’s useful to help our users to improve broker performance by operations. ### Goal 1. Provide per-thread CPU usage metrics. ### API Changes _No response_ ### Implementation Java provides MXBean to monitor JVM inner stats, I’ll implement per-thread CPU usage by [ThreadMXBean](https://github.com/openjdk/jdk/blob/master/src/java.management/share/classes/java/lang/management/ThreadMXBean.java). ### Alternatives _No response_ ### Anything else? _No response_ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@pulsar.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
