-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
[clusteragent/autoscaling] Implement stabilization for horizontal recommendations #31547
[clusteragent/autoscaling] Implement stabilization for horizontal recommendations #31547
Conversation
Test changes on VMUse this command from test-infra-definitions to manually test this PR changes on a VM: inv aws.create-vm --pipeline-id=51624624 --os-family=ubuntu Note: This applies to commit 1e6acbe |
go.mod
Outdated
@@ -160,7 +160,7 @@ require ( | |||
github.com/DataDog/datadog-agent/pkg/util/pointer v0.59.0 | |||
github.com/DataDog/datadog-agent/pkg/util/scrubber v0.59.0 | |||
github.com/DataDog/datadog-go/v5 v5.5.0 | |||
github.com/DataDog/datadog-operator v0.7.1-0.20241024104907-734366f3c0d1 | |||
github.com/DataDog/datadog-operator v0.7.1-0.20241111183642-43cd97e856a5 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
temporary; this is referencing this commit DataDog/datadog-operator#1519
Regression DetectorRegression Detector ResultsMetrics dashboard Baseline: 3763407 Optimization Goals: ✅ No significant changes detected
|
perf | experiment | goal | Δ mean % | Δ mean % CI | trials | links |
---|---|---|---|---|---|---|
➖ | uds_dogstatsd_to_api_cpu | % cpu utilization | +0.55 | [-0.13, +1.24] | 1 | Logs |
➖ | quality_gate_idle | memory utilization | +0.47 | [+0.44, +0.50] | 1 | Logs bounds checks dashboard |
➖ | file_to_blackhole_500ms_latency | egress throughput | +0.26 | [-0.52, +1.03] | 1 | Logs |
➖ | file_to_blackhole_0ms_latency_http1 | egress throughput | +0.15 | [-0.75, +1.05] | 1 | Logs |
➖ | file_to_blackhole_300ms_latency | egress throughput | +0.04 | [-0.62, +0.69] | 1 | Logs |
➖ | file_to_blackhole_100ms_latency | egress throughput | +0.01 | [-0.68, +0.70] | 1 | Logs |
➖ | file_to_blackhole_0ms_latency | egress throughput | +0.00 | [-0.91, +0.92] | 1 | Logs |
➖ | tcp_dd_logs_filter_exclude | ingress throughput | -0.01 | [-0.02, +0.01] | 1 | Logs |
➖ | uds_dogstatsd_to_api | ingress throughput | -0.01 | [-0.13, +0.11] | 1 | Logs |
➖ | file_to_blackhole_0ms_latency_http2 | egress throughput | -0.01 | [-0.85, +0.83] | 1 | Logs |
➖ | quality_gate_idle_all_features | memory utilization | -0.06 | [-0.14, +0.02] | 1 | Logs bounds checks dashboard |
➖ | file_to_blackhole_1000ms_latency_linear_load | egress throughput | -0.07 | [-0.54, +0.40] | 1 | Logs |
➖ | file_tree | memory utilization | -0.21 | [-0.34, -0.08] | 1 | Logs |
➖ | file_to_blackhole_1000ms_latency | egress throughput | -0.34 | [-1.13, +0.46] | 1 | Logs |
➖ | tcp_syslog_to_blackhole | ingress throughput | -1.27 | [-1.34, -1.21] | 1 | Logs |
➖ | otel_to_otel_logs | ingress throughput | -1.67 | [-2.36, -0.98] | 1 | Logs |
➖ | quality_gate_logs | % cpu utilization | -3.06 | [-6.25, +0.13] | 1 | Logs |
Bounds Checks: ✅ Passed
perf | experiment | bounds_check_name | replicates_passed | links |
---|---|---|---|---|
✅ | 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 | memory_usage | 10/10 | bounds checks dashboard |
✅ | quality_gate_idle_all_features | memory_usage | 10/10 | bounds checks dashboard |
✅ | quality_gate_logs | lost_bytes | 10/10 | |
✅ | quality_gate_logs | memory_usage | 10/10 |
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_idle_all_features, bounds check memory_usage: 10/10 replicas passed. Gate passed.
- quality_gate_idle, bounds check memory_usage: 10/10 replicas passed. Gate passed.
- quality_gate_logs, bounds check lost_bytes: 10/10 replicas passed. Gate passed.
- quality_gate_logs, bounds check memory_usage: 10/10 replicas passed. Gate passed.
@@ -204,6 +204,30 @@ func (hr *horizontalController) computeScaleAction( | |||
return nil, 0, errors.New(reason) | |||
} | |||
|
|||
var evalAfter time.Duration |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a reason why it's early in the flow? I would expect stabilization to be after the outsideBoundaries
check and after flooring targetDesiredReplicas
between min and max
?
return originalTargetDesiredReplicas, limitReason | ||
} | ||
|
||
upRecommendation := originalTargetDesiredReplicas |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could we use the scaleDirection
to only the necessary calculation?
Package size comparisonComparison with ancestor Diff per package
Decision |
Uncompressed package size comparisonComparison with ancestor Diff per package
Decision |
/merge |
Devflow running:
|
What does this PR do?
Implement stabilization for horizontal recommendations. Algorithm follows what is implemented for HPA.
Motivation
We want to be able to prevent frequent scaling actions being applied in the case of recommendation flapping.
Describe how to test/QA your changes
Possible Drawbacks / Trade-offs
Additional Notes
Relies on changes here DataDog/datadog-operator#1519