Guy.arbitman/usmon 790 remainder
What does this PR do?
Motivation
Additional Notes
Possible Drawbacks / Trade-offs
Describe how to test/QA your changes
Bloop Bleep... Dogbot Here
Regression Detector Results
Run ID: fdb2a70e-0e73-47db-9d1e-03eae41575dc Baseline: 2b5bbee1959ca2ac23f0c519312bad431c40fc36 Comparison: 63f8b48b9bcb1125177d1112ba4aaf288f924a83
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
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 | -0.87 | [-7.42, +5.68] |
Fine details of change detection per experiment
| perf | experiment | goal | Δ mean % | Δ mean % CI |
|---|---|---|---|---|
| ➖ | uds_dogstatsd_to_api_cpu | % cpu utilization | +0.67 | [-2.28, +3.63] |
| ➖ | process_agent_standard_check | memory utilization | +0.41 | [+0.38, +0.44] |
| ➖ | tcp_syslog_to_blackhole | ingress throughput | +0.40 | [+0.31, +0.50] |
| ➖ | process_agent_real_time_mode | memory utilization | +0.26 | [+0.22, +0.29] |
| ➖ | idle | memory utilization | +0.16 | [+0.11, +0.20] |
| ➖ | uds_dogstatsd_to_api | ingress throughput | -0.00 | [-0.20, +0.20] |
| ➖ | tcp_dd_logs_filter_exclude | ingress throughput | -0.00 | [-0.01, +0.00] |
| ➖ | trace_agent_msgpack | ingress throughput | -0.02 | [-0.03, -0.01] |
| ➖ | trace_agent_json | ingress throughput | -0.04 | [-0.07, +0.00] |
| ➖ | process_agent_standard_check_with_stats | memory utilization | -0.14 | [-0.17, -0.10] |
| ➖ | otel_to_otel_logs | ingress throughput | -0.38 | [-0.83, +0.06] |
| ➖ | file_to_blackhole | % cpu utilization | -0.87 | [-7.42, +5.68] |
| ➖ | file_tree | memory utilization | -1.05 | [-1.12, -0.98] |
| ➖ | basic_py_check | % cpu utilization | -1.80 | [-4.05, +0.45] |
| ➖ | pycheck_1000_100byte_tags | % cpu utilization | -2.80 | [-7.98, +2.39] |
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:
-
Its estimated |Δ mean %| ≥ 5.00%, indicating the change is big enough to merit a closer look.
-
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.
-
Its configuration does not mark it "erratic".