Skip to content

[backport][CWS] move all etw events in same goroutine as process events (#23316)#23334

Merged
dd-mergequeue[bot] merged 1 commit into
7.52.xfrom
paulcacheux/backport-23316
Mar 1, 2024
Merged

[backport][CWS] move all etw events in same goroutine as process events (#23316)#23334
dd-mergequeue[bot] merged 1 commit into
7.52.xfrom
paulcacheux/backport-23316

Conversation

@paulcacheux

@paulcacheux paulcacheux commented Mar 1, 2024

Copy link
Copy Markdown
Contributor

(cherry picked from commit 835f3bb)

What does this PR do?

manual backport of #23316

Motivation

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

@paulcacheux paulcacheux added this to the 7.52.0 milestone Mar 1, 2024
@paulcacheux
paulcacheux marked this pull request as ready for review March 1, 2024 13:36
@paulcacheux
paulcacheux requested a review from a team as a code owner March 1, 2024 13:36
@pr-commenter

pr-commenter Bot commented Mar 1, 2024

Copy link
Copy Markdown

Bloop Bleep... Dogbot Here

Regression Detector Results

Run ID: 0f0b850d-d8fc-40d7-b2b5-b8e01e49613e
Baseline: 668bb31
Comparison: b4bf420

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

Experiments with missing or malformed data

  • basic_py_check

Usually, this warning means that there is no usable optimization goal data for that experiment, which could be a result of misconfiguration.

No significant changes in experiment optimization goals

Confidence level: 90.00%
Effect size tolerance: |Δ mean %| ≥ 5.00%

There were no significant changes in experiment optimization goals at this confidence level and effect size tolerance.

Experiments ignored for regressions

Regressions in experiments with settings containing erratic: true are ignored.

perf experiment goal Δ mean % Δ mean % CI
file_to_blackhole % cpu utilization +0.20 [-6.36, +6.77]

Fine details of change detection per experiment

perf experiment goal Δ mean % Δ mean % CI
uds_dogstatsd_to_api_cpu % cpu utilization +0.82 [-0.59, +2.24]
process_agent_standard_check memory utilization +0.37 [+0.33, +0.41]
otel_to_otel_logs ingress throughput +0.34 [-0.31, +0.99]
tcp_syslog_to_blackhole ingress throughput +0.29 [+0.23, +0.34]
idle memory utilization +0.26 [+0.22, +0.29]
file_to_blackhole % cpu utilization +0.20 [-6.36, +6.77]
process_agent_standard_check_with_stats memory utilization +0.11 [+0.08, +0.15]
process_agent_real_time_mode memory utilization +0.07 [+0.04, +0.10]
trace_agent_msgpack ingress throughput +0.01 [-0.00, +0.03]
trace_agent_json ingress throughput +0.00 [-0.03, +0.04]
tcp_dd_logs_filter_exclude ingress throughput -0.00 [-0.00, +0.00]
uds_dogstatsd_to_api ingress throughput -0.00 [-0.00, +0.00]
file_tree memory utilization -0.21 [-0.29, -0.12]

Explanation

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:

  1. Its estimated |Δ mean %| ≥ 5.00%, indicating the change is big enough to merit a closer look.

  2. 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.

  3. Its configuration does not mark it "erratic".

@paulcacheux

Copy link
Copy Markdown
Contributor Author

/merge

@dd-devflow

dd-devflow Bot commented Mar 1, 2024

Copy link
Copy Markdown

🚂 MergeQueue

Pull request added to the queue.

This build is going to start soon! (estimated merge in less than 51m)

Use /merge -c to cancel this operation!

@dd-devflow

dd-devflow Bot commented Mar 1, 2024

Copy link
Copy Markdown

🚨 MergeQueue

Gitlab pipeline didn't start on its own and we were unable to create it... Please retry.

If you need support, contact us on Slack #ci-interfaces with those details!

@paulcacheux

Copy link
Copy Markdown
Contributor Author

/merge

@dd-devflow

dd-devflow Bot commented Mar 1, 2024

Copy link
Copy Markdown

🚂 MergeQueue

Pull request added to the queue.

This build is going to start soon! (estimated merge in less than 51m)

Use /merge -c to cancel this operation!

@dd-mergequeue
dd-mergequeue Bot merged commit be2939f into 7.52.x Mar 1, 2024
@dd-mergequeue
dd-mergequeue Bot deleted the paulcacheux/backport-23316 branch March 1, 2024 16:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants