async-profiler-advancedlisted

# Async-Profiler Advanced ## Purpose Choose a collection mechanism whose signal corresponds to the engineering question, prove what the runtime actually enabled, and state what the recording cannot establish. An async-profiler file is a sample of selected events under a particular stack walker, filter, rate limit, and access envelope—not a complete account of elapsed time. Async-profiler evolves quickly. Pin its release, keep the matching binary and converter, run `asprof -v`, `asprof list <pid>`, and `asprof --help`, and consult that tag's documentation. Never make a runbook depend on `master`, a historical option name, or an assumed fallback. The command reference is authored against async-profiler v4.5 for supported HotSpot targets on Linux/macOS; it is not a promise of support for native Windows, other JVM implementations, or every JDK update. Inspect the actual runtime build, container image, architecture and JVM flags; build toolchains alone may describe a different JVM. Keep profiler build requirements, target-JVM support and the converter's Java runtime separate. Do not upgrade the application, profiler or dependencies merely to make an example fit. ## Ownership boundary - Use `jfr-and-async-profiler` to choose the least-privileged first instrument. - Use this skill to configure and validate async-profiler itself. - Use `flame-graph-analysis` to reason from stack aggregates and differentials. - Use `allocation-profiling`, `concurrency-diagnostics`, and `off-heap