Allow profiling of workers with async-profiler

[bric3]

What Does This Do

Adds support for profiling worker threads using the async-profiler, enabling better performance analysis and diagnostics.

This code depends on having brew install async-profiler (Homebrew/homebrew-core#267881).

Motivation

gradle-profiler profiles the daemon only

Additional Notes

Contributor Checklist

• Format the title according to the contribution guidelines
• Assign the type: and (comp: or inst:) labels in addition to any other useful labels
• Avoid using close, fix, or any linking keywords when referencing an issue
  Use solves instead, and assign the PR milestone to the issue
• Update the CODEOWNERS file on source file addition, migration, or deletion
• Update public documentation with any new configuration flags or behaviors
• Add your completed PR to the merge queue by commenting /merge. You can also:
  • Customize the commit message associated with the merge with /merge --commit-message "..."
  • Remove your PR from the merge queue with /merge -c
  • Skip all merge queue checks with /merge -f --reason "reason"; please use this judiciously, as some checks do not run at the PR-level (note: the PR still needs to be mergeable, this will only skip the pre-merge build)
  • Get more information in this doc

Jira ticket: [PROJ-IDENT]

[jbachorik]

Any particular reason for not using our java-profiler?

[bric3]

@jbachorik I know async profiler and I contributed the async profiler formula to brew. Also, I don;t think we have a macos lib / distribution ?

[jbachorik]

@bric3 Ah, macos. Right. Fair enough. I was just probing what was the missing part to make async-profiler preferrable - this answers it :)

[bric3]

@jbachorik I would love it to have a macOs distribution ;)
I could profile IntelliJ (Jetbrains runtime) itself, and full of coroutines !

[dd-octo-sts]

🟢 Java Benchmark SLOs — All performance SLOs passed

Suite	Status
Startup	🟢 pass

SLO thresholds are defined here based on automatically generated metrics. A warning is raised when results are within 5% of the threshold.

PR vs. master results

Scenario	Candidate	master	Δ (95% CI of mean)
startup:insecure-bank:iast:Agent	14.03 s	13.93 s	[-0.2%; +1.7%] (no difference)
startup:insecure-bank:tracing:Agent	12.95 s	13.05 s	[-1.4%; -0.0%] (maybe better)
startup:petclinic:appsec:Agent	16.79 s	16.73 s	[-0.8%; +1.4%] (no difference)
startup:petclinic:iast:Agent	16.85 s	17.00 s	[-1.7%; -0.0%] (maybe better)
startup:petclinic:profiling:Agent	16.83 s	16.95 s	[-1.9%; +0.5%] (no difference)
startup:petclinic:sca:Agent	17.00 s	16.92 s	[-0.4%; +1.4%] (no difference)
startup:petclinic:tracing:Agent	16.17 s	16.21 s	[-1.4%; +0.9%] (no difference)

Commit: 4af4bc22 · CI Pipeline · Benchmarking Platform UI

---

Load and DaCapo benchmarks can be triggered manually in the GitLab pipeline. Results will appear in the Benchmarking Platform UI after completion.