Experiment with testing of dd-trace-java on GitLab on Windows OS

[AlexeyKuznetsov-DD]

DO NOT MERGE

What Does This Do

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
• Once approved, use merge queue to merge the PR

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	14.85 s	14.76 s	[-0.5%; +1.7%] (no difference)
startup:insecure-bank:tracing:Agent	13.66 s	13.66 s	[-0.7%; +0.7%] (no difference)
startup:petclinic:appsec:Agent	17.46 s	17.23 s	[+0.3%; +2.4%] (maybe worse)
startup:petclinic:iast:Agent	16.72 s	17.47 s	[-8.4%; -0.1%] (maybe better)
startup:petclinic:profiling:Agent	17.17 s	17.38 s	[-2.3%; -0.1%] (maybe better)
startup:petclinic:sca:Agent	17.39 s	17.34 s	[-0.4%; +1.0%] (no difference)
startup:petclinic:tracing:Agent	16.51 s	16.68 s	[-1.9%; -0.1%] (maybe better)

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