-
Notifications
You must be signed in to change notification settings - Fork 1.3k
[DEBUG-3986] dyninst/actuator: add a stateful control layer #37841
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
Conversation
Regression DetectorRegression Detector ResultsMetrics dashboard Baseline: 99942ff Optimization Goals: ✅ No significant changes detected
|
perf | experiment | goal | Δ mean % | Δ mean % CI | trials | links |
---|---|---|---|---|---|---|
➖ | quality_gate_logs | % cpu utilization | +2.14 | [-0.67, +4.96] | 1 | Logs bounds checks dashboard |
➖ | tcp_syslog_to_blackhole | ingress throughput | +1.05 | [+0.98, +1.11] | 1 | Logs |
➖ | uds_dogstatsd_to_api_cpu | % cpu utilization | +0.88 | [+0.04, +1.72] | 1 | Logs |
➖ | uds_dogstatsd_20mb_12k_contexts_20_senders | memory utilization | +0.73 | [+0.66, +0.80] | 1 | Logs |
➖ | quality_gate_idle | memory utilization | +0.56 | [+0.51, +0.62] | 1 | Logs bounds checks dashboard |
➖ | file_tree | memory utilization | +0.55 | [+0.39, +0.71] | 1 | Logs |
➖ | otlp_ingest_metrics | memory utilization | +0.30 | [+0.13, +0.47] | 1 | Logs |
➖ | ddot_logs | memory utilization | +0.28 | [+0.16, +0.40] | 1 | Logs |
➖ | ddot_metrics | memory utilization | +0.13 | [+0.01, +0.24] | 1 | Logs |
➖ | file_to_blackhole_0ms_latency_http1 | egress throughput | +0.10 | [-0.46, +0.66] | 1 | Logs |
➖ | otlp_ingest_logs | memory utilization | +0.10 | [-0.03, +0.23] | 1 | Logs |
➖ | file_to_blackhole_300ms_latency | egress throughput | +0.07 | [-0.55, +0.70] | 1 | Logs |
➖ | file_to_blackhole_0ms_latency_http2 | egress throughput | +0.06 | [-0.47, +0.59] | 1 | Logs |
➖ | file_to_blackhole_1000ms_latency_linear_load | egress throughput | +0.06 | [-0.18, +0.30] | 1 | Logs |
➖ | file_to_blackhole_500ms_latency | egress throughput | +0.02 | [-0.52, +0.57] | 1 | Logs |
➖ | file_to_blackhole_1000ms_latency | egress throughput | +0.01 | [-0.59, +0.62] | 1 | Logs |
➖ | tcp_dd_logs_filter_exclude | ingress throughput | +0.00 | [-0.02, +0.02] | 1 | Logs |
➖ | uds_dogstatsd_to_api | ingress throughput | -0.01 | [-0.28, +0.27] | 1 | Logs |
➖ | file_to_blackhole_0ms_latency | egress throughput | -0.06 | [-0.64, +0.52] | 1 | Logs |
➖ | file_to_blackhole_100ms_latency | egress throughput | -0.10 | [-0.62, +0.42] | 1 | Logs |
➖ | docker_containers_memory | memory utilization | -0.20 | [-0.28, -0.13] | 1 | Logs |
➖ | quality_gate_idle_all_features | memory utilization | -0.31 | [-0.38, -0.25] | 1 | Logs bounds checks dashboard |
➖ | docker_containers_cpu | % cpu utilization | -0.73 | [-3.71, +2.24] | 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_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.
- 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.
- quality_gate_logs, bounds check intake_connections: 10/10 replicas passed. Gate passed.
4acbdc3
to
2235b62
Compare
Static quality checks✅ Please find below the results from static quality gates Successful checksInfo
|
3dff4a2
to
779993c
Compare
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.
Neat tests!
pkg/dyninst/actuator/settings.go
Outdated
// UnregisterProgram unregisters a program from the dispatcher. | ||
UnregisterProgram(program ir.ProgramID) | ||
|
||
// HandleMessage handles a message from the dispatcher. |
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.
From a registered program?
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.
Fixed.
baseEvent | ||
programID ir.ProgramID | ||
err error | ||
} |
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 IR generation and compilation be combined into a single asynchronous action, that does both, in sequence? They both feel like steps of "probe initialization"? Maybe program loading too?
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.
Done.
pkg/dyninst/actuator/update.go
Outdated
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.
process.go maybe? it's not just update, and I think process might be clearer?
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.
Done.
pkg/dyninst/actuator/settings.go
Outdated
|
||
type settings struct { | ||
ringBufSize int | ||
dispatcher Dispatcher |
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.
Dispatcher wasn't too clear to me, before diving into code (as there is lots of dispatching going around with state machine). "Sink" maybe to indicate it has to do with dealing with output/results of the whole actuation? Or output or ProbeOutput or ProgramOutput?
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.
Called it MessageSink
.
779993c
to
88f2128
Compare
88f2128
to
544a643
Compare
/merge |
View all feedbacks in Devflow UI.
This merge request is not mergeable yet, because of pending checks/missing approvals. It will be added to the queue as soon as checks pass and/or get approvals.
The expected merge time in
|
This layer orchestrates the lifecycle of programs and how they map to processes. Most of the implementation and testing goes into the state machine and its updates. I suspect it could have a better implementation -- right now it's just a bunch of imperative case crushing. I tried to make up for that with a good deal of testing and testing infrastructure. The testing comes in two main forms: - TestSnapshot: uses golden files in a yaml DSL to list the set of events that should happen and then reports the state transitions and effects - TestStateMachineProperties: uses random event generation to try to shake out interesting behaviors Both of these tests rely on invariant checking of the state itself. In addition to the state, there's the implementation of the Actuator which hooks up the state machine and the effects it generates to real dependencies. One thing this change makes abundantly clear is the need to have fine-grained error reporting out of ir generation, and then separately a clearer interface for how to report these errors out into the diagnostics flows.
544a643
to
7b3f8a1
Compare
This layer orchestrates the lifecycle of programs and how they map to processes. Most of the implementation and testing goes into the state machine and its updates. I suspect it could have a better implementation -- right now it's just a bunch of imperative case crushing. I tried to make up for that with a good deal of testing and testing infrastructure.
The testing comes in two main forms:
Both of these tests rely on invariant checking of the state itself.
In addition to the state, there's the implementation of the Actuator which hooks up the state machine and the effects it generates to real dependencies.
One thing this change makes abundantly clear is the need to have fine-grained error reporting out of ir generation, and then separately a clearer interface for how to report these errors out into the diagnostics flows.