-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Fix static quality gates image suffix logic #37802
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix static quality gates image suffix logic #37802
Conversation
Static quality checks✅ Please find below the results from static quality gates Successful checksInfo
|
…/fix-static-quality-gates-image-suffix
Regression DetectorRegression Detector ResultsMetrics dashboard Baseline: 96e38c9 Optimization Goals: ✅ No significant changes detected
|
perf | experiment | goal | Δ mean % | Δ mean % CI | trials | links |
---|---|---|---|---|---|---|
➖ | file_tree | memory utilization | +1.67 | [+1.51, +1.83] | 1 | Logs |
➖ | docker_containers_cpu | % cpu utilization | +1.25 | [-1.73, +4.24] | 1 | Logs |
➖ | quality_gate_idle | memory utilization | +0.96 | [+0.89, +1.04] | 1 | Logs bounds checks dashboard |
➖ | quality_gate_logs | % cpu utilization | +0.72 | [-2.04, +3.47] | 1 | Logs bounds checks dashboard |
➖ | docker_containers_memory | memory utilization | +0.35 | [+0.28, +0.43] | 1 | Logs |
➖ | file_to_blackhole_0ms_latency | egress throughput | +0.15 | [-0.45, +0.74] | 1 | Logs |
➖ | file_to_blackhole_500ms_latency | egress throughput | +0.11 | [-0.54, +0.75] | 1 | Logs |
➖ | file_to_blackhole_1000ms_latency | egress throughput | +0.08 | [-0.51, +0.66] | 1 | Logs |
➖ | file_to_blackhole_0ms_latency_http2 | egress throughput | +0.08 | [-0.52, +0.67] | 1 | Logs |
➖ | file_to_blackhole_300ms_latency | egress throughput | +0.04 | [-0.60, +0.69] | 1 | Logs |
➖ | file_to_blackhole_0ms_latency_http1 | egress throughput | -0.00 | [-0.57, +0.57] | 1 | Logs |
➖ | tcp_dd_logs_filter_exclude | ingress throughput | -0.00 | [-0.02, +0.02] | 1 | Logs |
➖ | uds_dogstatsd_to_api | ingress throughput | -0.00 | [-0.28, +0.28] | 1 | Logs |
➖ | file_to_blackhole_1000ms_latency_linear_load | egress throughput | -0.01 | [-0.25, +0.22] | 1 | Logs |
➖ | file_to_blackhole_100ms_latency | egress throughput | -0.02 | [-0.61, +0.58] | 1 | Logs |
➖ | quality_gate_idle_all_features | memory utilization | -0.04 | [-0.14, +0.06] | 1 | Logs bounds checks dashboard |
➖ | ddot_metrics | memory utilization | -0.06 | [-0.18, +0.06] | 1 | Logs |
➖ | otlp_ingest_metrics | memory utilization | -0.19 | [-0.35, -0.03] | 1 | Logs |
➖ | otlp_ingest_logs | memory utilization | -0.24 | [-0.37, -0.12] | 1 | Logs |
➖ | ddot_logs | memory utilization | -0.37 | [-0.51, -0.23] | 1 | Logs |
➖ | uds_dogstatsd_20mb_12k_contexts_20_senders | memory utilization | -0.51 | [-0.56, -0.45] | 1 | Logs |
➖ | uds_dogstatsd_to_api_cpu | % cpu utilization | -0.82 | [-1.67, +0.04] | 1 | Logs |
➖ | tcp_syslog_to_blackhole | ingress throughput | -1.86 | [-1.92, -1.79] | 1 | Logs |
Bounds Checks: ✅ Passed
perf | experiment | bounds_check_name | replicates_passed | links |
---|---|---|---|---|
✅ | docker_containers_cpu | simple_check_run | 10/10 | |
✅ | docker_containers_memory | memory_usage | 10/10 | |
✅ | docker_containers_memory | simple_check_run | 10/10 | |
✅ | file_to_blackhole_0ms_latency | lost_bytes | 10/10 | |
✅ | file_to_blackhole_0ms_latency | memory_usage | 10/10 | |
✅ | file_to_blackhole_0ms_latency_http1 | lost_bytes | 10/10 | |
✅ | file_to_blackhole_0ms_latency_http1 | memory_usage | 10/10 | |
✅ | file_to_blackhole_0ms_latency_http2 | lost_bytes | 10/10 | |
✅ | file_to_blackhole_0ms_latency_http2 | memory_usage | 10/10 | |
✅ | file_to_blackhole_1000ms_latency | memory_usage | 10/10 | |
✅ | file_to_blackhole_1000ms_latency_linear_load | memory_usage | 10/10 | |
✅ | file_to_blackhole_100ms_latency | lost_bytes | 10/10 | |
✅ | file_to_blackhole_100ms_latency | memory_usage | 10/10 | |
✅ | file_to_blackhole_300ms_latency | lost_bytes | 10/10 | |
✅ | file_to_blackhole_300ms_latency | memory_usage | 10/10 | |
✅ | file_to_blackhole_500ms_latency | lost_bytes | 10/10 | |
✅ | file_to_blackhole_500ms_latency | memory_usage | 10/10 | |
✅ | quality_gate_idle | intake_connections | 10/10 | bounds checks dashboard |
✅ | quality_gate_idle | memory_usage | 10/10 | bounds checks dashboard |
✅ | quality_gate_idle_all_features | intake_connections | 10/10 | bounds checks dashboard |
✅ | quality_gate_idle_all_features | memory_usage | 10/10 | bounds checks dashboard |
✅ | quality_gate_logs | intake_connections | 10/10 | bounds checks dashboard |
✅ | quality_gate_logs | lost_bytes | 10/10 | bounds checks dashboard |
✅ | quality_gate_logs | memory_usage | 10/10 | bounds checks dashboard |
Explanation
Confidence level: 90.00%
Effect size tolerance: |Δ mean %| ≥ 5.00%
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
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".
CI Pass/Fail Decision
✅ Passed. All Quality Gates passed.
- quality_gate_logs, bounds check lost_bytes: 10/10 replicas passed. Gate passed.
- quality_gate_logs, bounds check intake_connections: 10/10 replicas passed. Gate passed.
- quality_gate_logs, bounds check memory_usage: 10/10 replicas passed. Gate passed.
- quality_gate_idle_all_features, bounds check intake_connections: 10/10 replicas passed. Gate passed.
- quality_gate_idle_all_features, bounds check memory_usage: 10/10 replicas passed. Gate passed.
- quality_gate_idle, bounds check intake_connections: 10/10 replicas passed. Gate passed.
- quality_gate_idle, bounds check memory_usage: 10/10 replicas passed. Gate passed.
/merge |
View all feedbacks in Devflow UI.
The expected merge time in
|
The backport to
To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-7.67.x 7.67.x
# Navigate to the new working tree
cd .worktrees/backport-7.67.x
# Create a new branch
git switch --create backport-37802-to-7.67.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 bea966a3165e2cce505f55aada6897b293932318
# Push it to GitHub
git push --set-upstream origin backport-37802-to-7.67.x
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-7.67.x Then, create a pull request where the |
(cherry picked from commit bea966a)
What does this PR do?
Fix the logic to compute static quality gates image suffix.
Parenthesis are needed to have the correct operation priority.
Also updates the static quality gates limits, increasing each by the diff with the previous value (so that the "margin" stays the same).
Motivation
Have correct numbers for
jmx
images.Describe how you validated your changes
Possible Drawbacks / Trade-offs
Additional Notes