Skip to content

performance/flaky-benchmarks-monitoring - #369

Draft
igoragoli wants to merge 1 commit into
mainfrom
performance/flaky-benchmarks-monitoring
Draft

igoragoli wants to merge 1 commit into
mainfrom
performance/flaky-benchmarks-monitoring

Conversation

@igoragoli

Copy link
Copy Markdown
Contributor

No description provided.

@pr-commenter

pr-commenter Bot commented Sep 20, 2026 •

Copy link
Copy Markdown

Benchmarks

Benchmark execution time: 2026-10-01 06:13:55

Comparing candidate commit 4145d1b in PR branch performance/flaky-benchmarks-monitoring with baseline commit df496e9 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 force-pushed the performance/flaky-benchmarks-monitoring branch from 2d0e022 to 2557125 Compare September 21, 2026 21:47
Generated by stability-generate-patch from
benchmarking-platform-tools patch-specs/dd-trace-cpp.yml.
Base: main @ df496e9.
Do not edit by hand — this branch is force-pushed on each refresh.
@igoragoli
igoragoli force-pushed the performance/flaky-benchmarks-monitoring branch from 2557125 to 4145d1b Compare September 30, 2026 09:40

This branch has not been deployed

No deployments
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