Comments (6)
Thank you for your interest in Async-profiler!
I'm not going to compare AP to HP in the documentation for several reasons (this won't be impartial anyway), but I'd like to write a blog post about the motivation of AP: why another tool was needed when there were already Honest Profiler and perf + Flame Graphs.
Meanwhile, before the post is out, I can highlight the main advantages of Async-profiler from my point of view:
- It samples all running code: not only Java, but native, JVM and even kernel functions, too.
- It has workarounds for annoying AsyncGetCallTrace bugs (see JDK-8178287). Async-profiler can show correct stack traces in the cases when other tools just fail with "AGCT::Unknown Java[ERR=-5]".
- Besides CPU profiling, it supports other profiling events like heap allocations, contended locks, perf events, kernel tracepoints.
- Attach-on-demand capability: it is not necessary to include the agent at application launch time.
However, what I like about Honest Profiler is its infrastructure around collecting and presenting data, including the GUI. In contrast, Async-profiler has just a command-line interface and a couple of output formats that can be visualized with external utilities like Flame Graph. This is not the primary direction of development, I'm not going to spend much time on it, but I'll be glad to accept contributions on the visualization side.
from async-profiler.
@zagorulkinde Here are the materials from my presentation at CodeOne: https://github.com/apangin/codeone2019-java-profiling
Unfortunately, the talk was not recorded, but I plan to make an article from it.
from async-profiler.
I've finally held a recorded webinar about async-profiler - 3.5 hours long!
https://www.youtube.com/playlist?list=PLNCLTEx3B8h4Yo_WvKWdLvI9mj1XpTKBr
Materials and code examples are available here.
This question is almost 3 year old now - so many things has changed during this time.
- UI is no longer a problem, since async-profiler has built-in FlameGraph and call tree generator.
- It also supports JFR format, compatible with JDK Mission Control and other tools.
- It can profile selected native functions and specified Java methods.
- It has wall-clock profiling mode.
- Since version 2.0, async-profiler is able to record multiple events simultaneously.
More improvements are listed on releases page.
I'd say, the main difference is that async-profiler is currently an active project, and I guess, the original question is not relevant anymore.
from async-profiler.
Cool thanks! I'd definitely be interested in a blog post but your comment is already quite helpful. We can leave this issue open until the blog post is up or just close it; either is fine with me.
from async-profiler.
Yep! That was my intent, too: the open issue will be an additional trigger for me to finish the post some time soon :)
from async-profiler.
@apangin Andrey hey! Do you have any progress with a blog post?
from async-profiler.
Related Issues (20)
- Introduce filtering by CPU HOT 1
- Compiling for arm32 fails HOT 3
- Profiling crashes in NMethod::isNMethod with JDK 23-ea HOT 3
- How can openjdk1.8 use async-profile -e alloc without installing debug symbols HOT 19
- What's the exact overhead of using cpu profiling? HOT 1
- Fails to build with Java >20 HOT 1
- Why Cannot StackTrace Be Found Using stackTraceId After LiveObject Is Enabled? HOT 11
- Support debuginfod HOT 1
- Why Are the Number of Threads and Thread IDs in the Profiler::instance()->threadFilter() Inaccurate? HOT 1
- build error when running make HOT 1
- Native errors when running async-profiler with JNI library HOT 2
- Segmentation fault on Azul Zing HOT 8
- `Unexpected EOF reading response` when running `asprof stop` after multiple collections HOT 2
- How to Enable Profiling in Kubernetes Pods? HOT 2
- Attach process is crash when asprof HOT 3
- Could not find agent library /mnt/libasyncProfiler.so in absolute path libstdc++.so.6: cannot open shared object file: No such file or directory HOT 7
- Cannot use BPF with asprof HOT 11
- Why'live' option is only supported on OpenJDK 11+, why JDK8 is not supported, is it a JDK limitation or async-profiler implementation limitation? HOT 1
- Converter with jfr2heat in main branch? HOT 2
- Fix broken JFR is possible? HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from async-profiler.