This project is a low overhead sampling profiler for Java that does not suffer from the Safepoint bias problem. It features HotSpot-specific API to collect stack traces and to track memory allocations. The profiler works with OpenJDK and other Java runtimes based on the HotSpot JVM.
Unlike traditional Java profilers, async-profiler monitors non-Java threads (e.g., GC and JIT compiler threads) and shows native and kernel frames in stack traces.
What can be profiled:
See our 3 hours playlist to learn about more features.
The most recent binaries corresponding to the latest successful commit in master.
For a build corresponding to one of the previous commits, go to Nightly Builds, click the desired build and scroll down to the artifacts section. These binaries are kept for 30 days.
In a typical use case, profiling a Java application is just a matter of a running asprof with a PID of a running Java process.
$ asprof -d 30 -f flamegraph.html <PID>
The above command translates to: run profiler for 30 seconds and save results to flamegraph.html as an interactive Flame Graph that can be viewed in a browser.
Find more details in the Getting started guide.
yum install libstdc++-static)Make sure gcc, g++ and java are available on the PATH. Navigate to the root directory with async-profiler sources and run make. async-profiler launcher will be available at build/bin/asprof.
Other Makefile targets:
make test - run unit and integration tests;make release - package async-profiler binaries as .tar.gz (Linux) or .zip (macOS).For known issues faced while running async-profiler and their detailed troubleshooting, please refer here.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4