Skip to content

performance/benchmark-flakiness-monitoring - #368

Closed
igoragoli wants to merge 1 commit into
mainfrom
performance/benchmark-flakiness-monitoring
Closed

igoragoli wants to merge 1 commit into
mainfrom
performance/benchmark-flakiness-monitoring

Conversation

@igoragoli

@igoragoli igoragoli commented Sep 19, 2026 •

Copy link
Copy Markdown
Contributor

No description provided.

Generated by stability-gen-patch from
benchmarking-platform-tools allowlists/DataDog-dd-trace-cpp.yml.
Base: main @ d7a2e2a.
Do not edit by hand — this branch is force-pushed on each refresh.
@igoragoli igoragoli changed the title ci: gate pipeline to benchmark jobs for stability monitoring performance/benchmark-flakiness-monitoring Sep 19, 2026
@pr-commenter

pr-commenter Bot commented Sep 19, 2026

Copy link
Copy Markdown

Benchmarks

Benchmark execution time: 2026-09-19 13:10:01

Comparing candidate commit e3491e9 in PR branch performance/benchmark-flakiness-monitoring with baseline commit d7a2e2a in branch main.

Found 0 performance improvements and 0 performance regressions! Performance is the same for 8 metrics, 0 unstable metrics.

Explanation

This is an A/B test comparing a candidate commit's performance against that of a baseline commit. Performance changes are noted in the tables below as:

  • 🟩 = significantly better candidate vs. baseline
  • 🟥 = significantly worse candidate vs. baseline

We compute a confidence interval (CI) over the relative difference of means between metrics from the candidate and baseline commits, considering the baseline as the reference.

If the CI is entirely outside the configured SIGNIFICANT_IMPACT_THRESHOLD (or the deprecated UNCONFIDENCE_THRESHOLD), the change is considered significant.

Feel free to reach out to #apm-benchmarking-platform on Slack if you have any questions.

More details about the CI and significant changes

You can imagine this CI as a range of values that is likely to contain the true difference of means between the candidate and baseline commits.

CIs of the difference of means are often centered around 0%, because often changes are not that big:

---------------------------------(------|---^--------)-------------------------------->
                              -0.6%    0%  0.3%     +1.2%
                                 |          |        |
         lower bound of the CI --'          |        |
sample mean (center of the CI) -------------'        |
         upper bound of the CI ----------------------'

As described above, a change is considered significant if the CI is entirely outside the configured SIGNIFICANT_IMPACT_THRESHOLD (or the deprecated UNCONFIDENCE_THRESHOLD).

For instance, for an execution time metric, this confidence interval indicates a significantly worse performance:

----------------------------------------|---------|---(---------^---------)---------->
                                       0%        1%  1.3%      2.2%      3.1%
                                                  |   |         |         |
       significant impact threshold --------------'   |         |         |
                      lower bound of CI --------------'         |         |
       sample mean (center of the CI) --------------------------'         |
                      upper bound of CI ----------------------------------'

@igoragoli igoragoli closed this Sep 20, 2026
@igoragoli
igoragoli deleted the performance/benchmark-flakiness-monitoring branch September 20, 2026 15:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant