-
Notifications
You must be signed in to change notification settings - Fork 1.3k
WINA-1171: CPU info rework #37528
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
WINA-1171: CPU info rework #37528
Conversation
Regression DetectorRegression Detector ResultsMetrics dashboard Baseline: e1d209a Optimization Goals: ✅ No significant changes detected
|
perf | experiment | goal | Δ mean % | Δ mean % CI | trials | links |
---|---|---|---|---|---|---|
➖ | quality_gate_logs | % cpu utilization | +4.29 | [+1.51, +7.06] | 1 | Logs bounds checks dashboard |
➖ | docker_containers_memory | memory utilization | +0.71 | [+0.65, +0.76] | 1 | Logs |
➖ | docker_containers_cpu | % cpu utilization | +0.61 | [-2.41, +3.63] | 1 | Logs |
➖ | quality_gate_idle_all_features | memory utilization | +0.43 | [+0.35, +0.51] | 1 | Logs bounds checks dashboard |
➖ | file_tree | memory utilization | +0.43 | [+0.27, +0.58] | 1 | Logs |
➖ | otlp_ingest_metrics | memory utilization | +0.36 | [+0.19, +0.52] | 1 | Logs |
➖ | quality_gate_idle | memory utilization | +0.29 | [+0.23, +0.35] | 1 | Logs bounds checks dashboard |
➖ | file_to_blackhole_0ms_latency | egress throughput | +0.11 | [-0.44, +0.65] | 1 | Logs |
➖ | file_to_blackhole_300ms_latency | egress throughput | +0.10 | [-0.52, +0.72] | 1 | Logs |
➖ | file_to_blackhole_0ms_latency_http2 | egress throughput | +0.03 | [-0.54, +0.60] | 1 | Logs |
➖ | file_to_blackhole_500ms_latency | egress throughput | +0.01 | [-0.59, +0.62] | 1 | Logs |
➖ | file_to_blackhole_1000ms_latency | egress throughput | +0.01 | [-0.58, +0.60] | 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.26] | 1 | Logs |
➖ | file_to_blackhole_0ms_latency_http1 | egress throughput | -0.02 | [-0.64, +0.60] | 1 | Logs |
➖ | ddot_metrics | memory utilization | -0.04 | [-0.16, +0.08] | 1 | Logs |
➖ | file_to_blackhole_1000ms_latency_linear_load | egress throughput | -0.07 | [-0.31, +0.16] | 1 | Logs |
➖ | file_to_blackhole_100ms_latency | egress throughput | -0.08 | [-0.66, +0.50] | 1 | Logs |
➖ | ddot_logs | memory utilization | -0.10 | [-0.24, +0.03] | 1 | Logs |
➖ | uds_dogstatsd_20mb_12k_contexts_20_senders | memory utilization | -0.32 | [-0.37, -0.27] | 1 | Logs |
➖ | otlp_ingest_logs | memory utilization | -0.39 | [-0.52, -0.26] | 1 | Logs |
➖ | uds_dogstatsd_to_api_cpu | % cpu utilization | -0.98 | [-1.84, -0.12] | 1 | Logs |
➖ | tcp_syslog_to_blackhole | ingress throughput | -3.13 | [-3.21, -3.05] | 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_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 memory_usage: 10/10 replicas passed. Gate passed.
- quality_gate_idle, 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 intake_connections: 10/10 replicas passed. Gate passed.
- quality_gate_logs, bounds check lost_bytes: 10/10 replicas passed. Gate passed.
Static quality checks✅ Please find below the results from static quality gates Successful checksInfo
|
releasenotes/notes/windows-agent-cpu-info-18e54faf1ffbd15a.yaml
Outdated
Show resolved
Hide resolved
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.
Left a few comments and suggestions
releasenotes/notes/windows-agent-cpu-info-18e54faf1ffbd15a.yaml
Outdated
Show resolved
Hide resolved
…taDog/datadog-agent into hongshi.guo/WINA-1171_cpu_info_rework sync up with remote branch
/merge |
View all feedbacks in Devflow UI.
The expected merge time in
|
What does this PR do?
This PR addresses the issue of inaccurate cpu_cores reported by "gohai". Specifically, The system.cpu.num_cores metric could be wrong on certain Windows platforms. This PR intends to retrieve the correct CPU data from Windows systems across Windows platforms and independent of CPU architecture, providing a generic solution to CPU metric data.
Relevant JIRA cases are:
Motivation
Both external customers and internal users have reported similar issues, the Windows Agent team also reproduced the issue. Inaccurate data could lead to user confusion.
Describe how you validated your changes
The issue can be reproduced relatively easily, which helped develop and validate the solution. The changes were verified by running the test command on the systems which reproduced the problem. Use the following command for local test: go test -tags=test -v ./pkg/gohai/cpu
Possible Drawbacks / Trade-offs
Additional Notes
Based on the investigation, the previous implementation retrieves data from native system calls on Windows, and there were assumptions of certain data sizes and hardcoded data offset values, which was potentially risky and resulted in incorrect data retrieved. This PR removes the above assumptions and made data collection independent of CPU architecture., which means we let the OS do the heavy lifting and use the data provided by the system to figure out the location of each CPU record.