Update APM SDK benchmarks reference

[dd-octo-sts]

What Does This Do

This PR updates the pinned apm-sdks-benchmarks GitLab CI includes and runtime clones to
DataDog/apm-sdks-benchmarks@454a97647cbc16ab7fd20e917aa31532ba7532eb.

Motivation

Keep Java SDK benchmarks current while retaining reproducible CI configuration.

Contributor Checklist

• Verify CI passes successfully

[datadog-datadog-prod-us1-2]

More details

The shared SHA anchor consistently updates every benchmark CI include and the runtime clone variable to the same pinned revision.

Was this helpful? React 👍 or 👎

_{Open Bits AI session}

_{🤖 Bits Code Review · Commit aeb194d · @DataDog review to ask questions}

[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	13.95 s	13.95 s	[-0.8%; +0.8%] (no difference)
startup:insecure-bank:tracing:Agent	12.98 s	13.03 s	[-1.2%; +0.4%] (no difference)
startup:petclinic:appsec:Agent	17.28 s	17.17 s	[-0.3%; +1.6%] (no difference)
startup:petclinic:iast:Agent	16.41 s	17.17 s	[-8.7%; -0.2%] (maybe better)
startup:petclinic:profiling:Agent	16.60 s	16.94 s	[-3.3%; -0.7%] (maybe better)
startup:petclinic:sca:Agent	17.19 s	17.09 s	[-0.2%; +1.4%] (no difference)
startup:petclinic:tracing:Agent	16.21 s	16.28 s	[-1.5%; +0.5%] (no difference)

Commit: aeb194d7 · 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.

[AlexeyKuznetsov-DD]

/merge -f --reason "No need to run MQ, validated in PR"

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-10-07 18:15:56 UTC ℹ️ Start processing command /merge -f --reason "No need to run MQ, validated in PR"

---

2026-10-07 18:16:00 UTC ℹ️ MergeQueue: pull request added to the queue

The expected merge time in master is approximately 0s (p90).

---

2026-10-07 18:16:11 UTC ℹ️ MergeQueue: This merge request was merged

Warning

This change was merged without running any pre merge CI checks

Reason: No need to run MQ, validated in PR