riemann-jvm-profiler
riemann-jvm-profiler copied to clipboard
differences with async-profiler
async-profiler says it avoids safepoint problem in its README and a low-level profile for jvm-applications.
I'm curious if riemann-jvm-profiler also avoid safepoint, and what's more or less compared with async-profile, Thanks in advance.
Nope, those APIs didn't exist at the time I wrote this. You're welcome to port async-profiler's methods to Riemann-JVM-profiler, though.On Apr 9, 2018 03:17, Jiacai Liu [email protected] wrote:async-profiler says it avoids safepoint problem in its README and a low-level profile for jvm-applications. I'm curious if riemann-jvm-profiler also avoid safepoint, and what's more or less compared with async-profile, Thanks in advance.
—You are receiving this because you are subscribed to this thread.Reply to this email directly, view it on GitHub, or mute the thread.
As far as I can tell from the source code, it uses ThreadMXBean to get stack traces, which is subject to the safepoint bias.
Thank your guys, I will try to port async-profile's method to Riemann-JVM-profiler.