Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

differences with async-profiler #9

Open
jiacai2050 opened this issue Apr 9, 2018 · 3 comments
Open

differences with async-profiler #9

jiacai2050 opened this issue Apr 9, 2018 · 3 comments

Comments

@jiacai2050
Copy link

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.

@aphyr
Copy link
Contributor

aphyr commented Apr 9, 2018 via email

@goldshtn
Copy link

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

@jiacai2050
Copy link
Author

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants