[CIREL] test: Run tests on new Windows AMI

[BaptisteLalanne]

trafficstars

What does this PR do?

Motivation

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

[bits-bot]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[pr-commenter[bot]]

Bloop Bleep... Dogbot Here

Regression Detector Results

Run ID: b0845b07-34a2-491e-b833-afe7e4129fc0 Baseline: 6a26db5af052c0b1f825909e9489e83b2577972d Comparison: 2df2ec6275f7ad9d13bd6598d49005960d36fe4e Total CPUs: 7

Performance changes are noted in the perf column of each table:

• ✅ = significantly better comparison variant performance
• ❌ = significantly worse comparison variant performance
• ➖ = no significant change in performance

Experiments with missing or malformed data

• basic_py_check

Usually, this warning means that there is no usable optimization goal data for that experiment, which could be a result of misconfiguration.

No significant changes in experiment optimization goals

Confidence level: 90.00% Effect size tolerance: |Δ mean %| ≥ 5.00%

There were no significant changes in experiment optimization goals at this confidence level and effect size tolerance.

Experiments ignored for regressions

Regressions in experiments with settings containing erratic: true are ignored.

perf	experiment	goal	Δ mean %	Δ mean % CI
➖	file_to_blackhole	% cpu utilization	-1.75	[-8.28, +4.78]

Fine details of change detection per experiment

perf	experiment	goal	Δ mean %	Δ mean % CI
➖	otel_to_otel_logs	ingress throughput	+2.67	[+2.05, +3.28]
➖	uds_dogstatsd_to_api_cpu	% cpu utilization	+1.37	[-0.06, +2.80]
➖	process_agent_real_time_mode	memory utilization	+0.42	[+0.39, +0.45]
➖	tcp_syslog_to_blackhole	ingress throughput	+0.14	[+0.07, +0.21]
➖	process_agent_standard_check_with_stats	memory utilization	+0.08	[+0.04, +0.12]
➖	file_tree	memory utilization	+0.04	[-0.04, +0.12]
➖	trace_agent_msgpack	ingress throughput	+0.02	[+0.01, +0.02]
➖	tcp_dd_logs_filter_exclude	ingress throughput	+0.00	[-0.00, +0.00]
➖	trace_agent_json	ingress throughput	+0.00	[-0.01, +0.01]
➖	uds_dogstatsd_to_api	ingress throughput	+0.00	[-0.00, +0.00]
➖	process_agent_standard_check	memory utilization	-0.28	[-0.32, -0.24]
➖	idle	memory utilization	-0.44	[-0.46, -0.41]
➖	file_to_blackhole	% cpu utilization	-1.75	[-8.28, +4.78]

Explanation

A regression test is an A/B test of target performance in a repeatable rig, where "performance" is measured as "comparison variant minus baseline variant" for an optimization goal (e.g., ingress throughput). Due to intrinsic variability in measuring that goal, we can only estimate its mean value for each experiment; we report uncertainty in that value as a 90.00% confidence interval denoted "Δ mean % CI".

For each experiment, we decide whether a change in performance is a "regression" -- a change worth investigating further -- if all of the following criteria are true:

1. Its estimated |Δ mean %| ≥ 5.00%, indicating the change is big enough to merit a closer look.

2. Its 90.00% confidence interval "Δ mean % CI" does not contain zero, indicating that if our statistical model is accurate, there is at least a 90.00% chance there is a difference in performance between baseline and comparison variants.

3. Its configuration does not mark it "erratic".