riemann-jvm-profiler icon indicating copy to clipboard operation
riemann-jvm-profiler copied to clipboard

differences with async-profiler

Open jiacai2050 opened this issue 7 years ago • 3 comments

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.

jiacai2050 avatar Apr 09 '18 08:04 jiacai2050

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.

aphyr avatar Apr 09 '18 12:04 aphyr

As far as I can tell from the source code, it uses ThreadMXBean to get stack traces, which is subject to the safepoint bias.

goldshtn avatar Apr 10 '18 05:04 goldshtn

Thank your guys, I will try to port async-profile's method to Riemann-JVM-profiler.

jiacai2050 avatar Apr 23 '18 08:04 jiacai2050