Test sarahchen6/add-sca-benchmarks branch of apm-sdks-benchmarks

[sarahchen6]

What Does This Do

Test changes made in https://github.com/DataDog/apm-sdks-benchmarks/pull/161

Motivation

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
  • Get more information in this doc

Jira ticket: [PROJ-IDENT]

[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.93 s	14.02 s	[-1.4%; +0.1%] (no difference)
startup:insecure-bank:tracing:Agent	12.94 s	12.92 s	[-1.0%; +1.4%] (no difference)
startup:petclinic:appsec:Agent	16.86 s	16.85 s	[-1.0%; +1.2%] (no difference)
startup:petclinic:iast:Agent	16.89 s	16.98 s	[-1.7%; +0.6%] (no difference)
startup:petclinic:profiling:Agent	16.78 s	16.84 s	[-1.4%; +0.7%] (no difference)
startup:petclinic:sca:Agent	16.71 s	16.82 s	[-2.3%; +1.0%] (no difference)
startup:petclinic:tracing:Agent	15.95 s	16.25 s	[-3.3%; -0.5%] (maybe better)

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