-
Notifications
You must be signed in to change notification settings - Fork 1.3k
[dyninst] Testing expansion #37744
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
[dyninst] Testing expansion #37744
Conversation
5488e33
to
2739c32
Compare
2739c32
to
6a12148
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.
🚢 🇮🇹
Seeing the generated code makes it so clear we should find a way to just stick this into const data maps and stop compiling on the host
SM_OP_PREPARE_EVENT_ROOT, 0x2a, 0x00, 0x00, 0x00, 0x09, 0x00, 0x00, 0x00, | ||
SM_OP_CALL, 0x9b, 0x00, 0x00, 0x00, // ProcessExpression[Probe[main.inlined]@0x491c66.expr[0]] | ||
SM_OP_RETURN, | ||
SM_OP_ILLEGAL, |
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.
nit: inject some commentary around the padding?
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
Regression DetectorRegression Detector ResultsMetrics dashboard Baseline: 6e862a9 Optimization Goals: ✅ No significant changes detected
|
perf | experiment | goal | Δ mean % | Δ mean % CI | trials | links |
---|---|---|---|---|---|---|
➖ | quality_gate_idle_all_features | memory utilization | +0.72 | [+0.63, +0.81] | 1 | Logs bounds checks dashboard |
➖ | uds_dogstatsd_to_api_cpu | % cpu utilization | +0.64 | [-0.21, +1.48] | 1 | Logs |
➖ | otlp_ingest_logs | memory utilization | +0.48 | [+0.35, +0.60] | 1 | Logs |
➖ | quality_gate_idle | memory utilization | +0.32 | [+0.26, +0.38] | 1 | Logs bounds checks dashboard |
➖ | file_tree | memory utilization | +0.25 | [+0.10, +0.40] | 1 | Logs |
➖ | uds_dogstatsd_20mb_12k_contexts_20_senders | memory utilization | +0.15 | [+0.10, +0.19] | 1 | Logs |
➖ | file_to_blackhole_1000ms_latency | egress throughput | +0.11 | [-0.46, +0.68] | 1 | Logs |
➖ | quality_gate_logs | % cpu utilization | +0.08 | [-2.65, +2.82] | 1 | Logs bounds checks dashboard |
➖ | file_to_blackhole_0ms_latency_http2 | egress throughput | +0.05 | [-0.55, +0.65] | 1 | Logs |
➖ | ddot_metrics | memory utilization | +0.03 | [-0.09, +0.15] | 1 | Logs |
➖ | ddot_logs | memory utilization | +0.00 | [-0.14, +0.15] | 1 | Logs |
➖ | tcp_dd_logs_filter_exclude | ingress throughput | +0.00 | [-0.01, +0.02] | 1 | Logs |
➖ | file_to_blackhole_1000ms_latency_linear_load | egress throughput | +0.00 | [-0.23, +0.24] | 1 | Logs |
➖ | uds_dogstatsd_to_api | ingress throughput | -0.00 | [-0.29, +0.28] | 1 | Logs |
➖ | file_to_blackhole_100ms_latency | egress throughput | -0.04 | [-0.63, +0.55] | 1 | Logs |
➖ | file_to_blackhole_0ms_latency | egress throughput | -0.04 | [-0.67, +0.58] | 1 | Logs |
➖ | docker_containers_memory | memory utilization | -0.05 | [-0.13, +0.03] | 1 | Logs |
➖ | file_to_blackhole_500ms_latency | egress throughput | -0.06 | [-0.69, +0.57] | 1 | Logs |
➖ | file_to_blackhole_300ms_latency | egress throughput | -0.06 | [-0.64, +0.51] | 1 | Logs |
➖ | file_to_blackhole_0ms_latency_http1 | egress throughput | -0.09 | [-0.70, +0.52] | 1 | Logs |
➖ | otlp_ingest_metrics | memory utilization | -0.16 | [-0.32, +0.00] | 1 | Logs |
➖ | tcp_syslog_to_blackhole | ingress throughput | -1.44 | [-1.50, -1.37] | 1 | Logs |
➖ | docker_containers_cpu | % cpu utilization | -3.11 | [-6.10, -0.11] | 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 memory_usage: 10/10 replicas passed. Gate passed.
- quality_gate_idle, 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_all_features, 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_logs, bounds check lost_bytes: 10/10 replicas passed. Gate passed.
- quality_gate_logs, bounds check intake_connections: 10/10 replicas passed. Gate passed.
6ef843b
to
7aa430b
Compare
7aa430b
to
b299da6
Compare
Static quality checks✅ Please find below the results from static quality gates Successful checksInfo
|
b299da6
to
83ab8a0
Compare
83ab8a0
to
b137bb4
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.
devflow unqueued this merge request: It did not become mergeable within the expected time |
rewrite, _ := strconv.ParseBool(os.Getenv("REWRITE")) | ||
return rewrite | ||
}() | ||
var rewrite = flag.Bool("rewrite", rewriteFromEnv, "rewrite the test files") |
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.
I'm surprised there isn't some existing machinery for snapshots, golden files, and rewrites already?
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.
There definitely are, not sure how popular within datadog. However, we are looking for something really simple, while knowing exactly how we want to manage these files. I think a bar to use a framework has not been reached.
b137bb4
to
689913d
Compare
/merge |
View all feedbacks in Devflow UI.
PR already in the queue with status waiting |
Loading is testing in integration test. For compiler test it's worth seeing the generated code.
738cc84
to
c696732
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
|
What does this PR do?
Share probe configs across tests.
Add snapshot test for compiler, dropping old, temporary test.
Merge simple and events_simple testprogs, they end up being almost the same.
Fix arm cfa offset calculation, exposed by more test cases.
Motivation
https://datadoghq.atlassian.net/browse/DEBUG-3887