-
Notifications
You must be signed in to change notification settings - Fork 1.3k
[clusteragent/autoscaling] Allow configuring local fallback activation threshold #37581
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] Allow configuring local fallback activation threshold #37581
Conversation
Regression DetectorRegression Detector ResultsMetrics dashboard Baseline: 7a0a040 Optimization Goals: ✅ No significant changes detected
|
perf | experiment | goal | Δ mean % | Δ mean % CI | trials | links |
---|---|---|---|---|---|---|
➖ | uds_dogstatsd_20mb_12k_contexts_20_senders | memory utilization | +0.15 | [+0.09, +0.21] | 1 | Logs |
➖ | docker_containers_memory | memory utilization | +0.12 | [+0.06, +0.19] | 1 | Logs |
➖ | otlp_ingest_metrics | memory utilization | +0.11 | [-0.06, +0.28] | 1 | Logs |
➖ | file_to_blackhole_0ms_latency | egress throughput | +0.09 | [-0.48, +0.67] | 1 | Logs |
➖ | ddot_logs | memory utilization | +0.04 | [-0.10, +0.18] | 1 | Logs |
➖ | file_to_blackhole_0ms_latency_http2 | egress throughput | +0.04 | [-0.58, +0.65] | 1 | Logs |
➖ | file_to_blackhole_1000ms_latency_linear_load | egress throughput | +0.03 | [-0.20, +0.26] | 1 | Logs |
➖ | file_to_blackhole_0ms_latency_http1 | egress throughput | +0.02 | [-0.53, +0.56] | 1 | Logs |
➖ | file_to_blackhole_500ms_latency | egress throughput | +0.01 | [-0.60, +0.63] | 1 | Logs |
➖ | uds_dogstatsd_to_api | ingress throughput | +0.01 | [-0.27, +0.30] | 1 | Logs |
➖ | file_to_blackhole_300ms_latency | egress throughput | +0.01 | [-0.59, +0.60] | 1 | Logs |
➖ | tcp_dd_logs_filter_exclude | ingress throughput | +0.00 | [-0.01, +0.02] | 1 | Logs |
➖ | quality_gate_idle_all_features | memory utilization | -0.01 | [-0.08, +0.06] | 1 | Logs bounds checks dashboard |
➖ | file_to_blackhole_1000ms_latency | egress throughput | -0.05 | [-0.70, +0.60] | 1 | Logs |
➖ | file_to_blackhole_100ms_latency | egress throughput | -0.08 | [-0.66, +0.51] | 1 | Logs |
➖ | otlp_ingest_logs | memory utilization | -0.14 | [-0.27, -0.02] | 1 | Logs |
➖ | ddot_metrics | memory utilization | -0.19 | [-0.31, -0.08] | 1 | Logs |
➖ | file_tree | memory utilization | -0.56 | [-0.71, -0.41] | 1 | Logs |
➖ | uds_dogstatsd_to_api_cpu | % cpu utilization | -0.66 | [-1.53, +0.20] | 1 | Logs |
➖ | quality_gate_idle | memory utilization | -0.73 | [-0.78, -0.67] | 1 | Logs bounds checks dashboard |
➖ | tcp_syslog_to_blackhole | ingress throughput | -0.88 | [-0.93, -0.83] | 1 | Logs |
➖ | quality_gate_logs | % cpu utilization | -1.78 | [-4.52, +0.96] | 1 | Logs bounds checks dashboard |
➖ | docker_containers_cpu | % cpu utilization | -2.31 | [-5.31, +0.70] | 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 memory_usage: 10/10 replicas passed. Gate passed.
- quality_gate_logs, bounds check intake_connections: 10/10 replicas passed. Gate passed.
- quality_gate_logs, bounds check lost_bytes: 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.
- 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.
Static quality checks✅ Please find below the results from static quality gates Successful checksInfo
|
dfaeacc
to
b608d3a
Compare
@@ -517,19 +517,25 @@ func getActiveScalingSources(currentTime time.Time, podAutoscalerInternal *model | |||
fallbackHorizontalScalingValues := podAutoscalerInternal.FallbackScalingValues().Horizontal | |||
|
|||
// If main scaling values are not stale, use those | |||
if mainHorizontalScalingValues != nil && !isTimestampStale(currentTime, mainHorizontalScalingValues.Timestamp) { | |||
if mainHorizontalScalingValues != nil && !isTimestampStale(currentTime, mainHorizontalScalingValues.Timestamp, nil) { |
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.
Shouldn't that check the staleness compared with the setting? If I want a local fallback after 5mins, this will return true while it should not
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.
updated!
/merge |
View all feedbacks in Devflow UI.
The expected merge time in
|
What does this PR do?
Allow configuring local fallback activation threshold by setting the following in the DPA:
Also change the default threshold to activate local fallback to
30 minutes
Motivation
Previously,
staleRecommendationThresholdSeconds
controlled when a metric would be considered stale when calculating the local fallback recommendations, even though the documentation had it intended to control when local fallback would be activated.Describe how you validated your changes
staleRecommendationThresholdSeconds
Possible Drawbacks / Trade-offs
We no longer give users the ability to control which metrics are considered stale for the purposes of local fallback recommendations (by default we use a timeframe of
60s
).Additional Notes