Skip to content

feat: enable sccache before the benchmarking runs - #2434

Draft
Aaalibaba42 wants to merge 1 commit into
mainfrom
jwiriath/APMSP-3981-sccache-on-benchmarking-platform
Draft

feat: enable sccache before the benchmarking runs#2434
Aaalibaba42 wants to merge 1 commit into
mainfrom
jwiriath/APMSP-3981-sccache-on-benchmarking-platform

Conversation

@Aaalibaba42

Copy link
Copy Markdown
Contributor

What does this PR do?

Enable sccache on the benchmarking platform jobs.

Motivation

Benchmarks are one of the most time consuming parts on the ci, and building against main should have full cache hits, whilst building against the branch should have partial cache hits, either way should be a net win.

Additional Notes

Benchmarking platform side is not yet merged, so this is draft and expected to fail for now

@datadog-datadog-prod-us1-2

datadog-datadog-prod-us1-2 Bot commented Aug 28, 2026

Copy link
Copy Markdown

Pipelines

🎯 Code Coverage (details)
Patch Coverage: 100.00%
Overall Coverage: 76.65% (-0.01%)

This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 0771bb4 | Docs | View more details | Give us feedback!

@pr-commenter

pr-commenter Bot commented Aug 28, 2026

Copy link
Copy Markdown

Benchmarks

Comparison

Benchmark execution time: 2026-08-28 16:03:29

Comparing candidate commit 0771bb4 in PR branch jwiriath/APMSP-3981-sccache-on-benchmarking-platform with baseline commit aa13755 in branch main.

Found 16 performance improvements and 9 performance regressions! Performance is the same for 143 metrics, 10 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 ----------------------------------'

scenario:credit_card/is_card_number/ 3782-8224-6310-005

  • 🟩 execution_time [-5.254µs; -5.091µs] or [-6.574%; -6.370%]
  • 🟩 throughput [+852321.610op/s; +879127.535op/s] or [+6.812%; +7.026%]

scenario:credit_card/is_card_number/ 378282246310005

  • 🟩 execution_time [-5.019µs; -4.886µs] or [-6.837%; -6.657%]
  • 🟩 throughput [+972841.979op/s; +997556.195op/s] or [+7.141%; +7.322%]

scenario:credit_card/is_card_number/378282246310005

  • 🟩 execution_time [-4.900µs; -4.783µs] or [-6.993%; -6.826%]
  • 🟩 throughput [+1046859.680op/s; +1070669.030op/s] or [+7.335%; +7.502%]

scenario:credit_card/is_card_number/37828224631000521389798

  • 🟩 execution_time [-6.462µs; -6.434µs] or [-12.344%; -12.290%]
  • 🟩 throughput [+2677005.406op/s; +2689601.009op/s] or [+14.014%; +14.080%]

scenario:credit_card/is_card_number/x371413321323331

  • 🟥 execution_time [+599.396ns; +602.511ns] or [+9.908%; +9.959%]
  • 🟥 throughput [-14973828.086op/s; -14898777.492op/s] or [-9.059%; -9.013%]

scenario:credit_card/is_card_number_no_luhn/ 378282246310005

  • 🟩 execution_time [-5.307µs; -5.268µs] or [-9.020%; -8.953%]
  • 🟩 throughput [+1672121.645op/s; +1683806.485op/s] or [+9.839%; +9.908%]

scenario:credit_card/is_card_number_no_luhn/378282246310005

  • 🟩 execution_time [-5.173µs; -5.134µs] or [-9.323%; -9.253%]
  • 🟩 throughput [+1838671.581op/s; +1851617.643op/s] or [+10.202%; +10.274%]

scenario:credit_card/is_card_number_no_luhn/37828224631000521389798

  • 🟩 execution_time [-6.457µs; -6.428µs] or [-12.334%; -12.280%]
  • 🟩 throughput [+2674440.373op/s; +2687189.951op/s] or [+14.001%; +14.068%]

scenario:credit_card/is_card_number_no_luhn/x371413321323331

  • 🟥 execution_time [+596.426ns; +600.243ns] or [+9.858%; +9.921%]
  • 🟥 throughput [-14920913.163op/s; -14830098.979op/s] or [-9.027%; -8.972%]

scenario:datadog_sample_span/tag_rule_matching/wall_time

  • 🟥 execution_time [+18.142ns; +18.277ns] or [+5.579%; +5.621%]

scenario:glob_matcher/ascii_case_insensitive_match/wall_time

  • 🟥 execution_time [+2.940ns; +2.954ns] or [+11.022%; +11.072%]

scenario:glob_matcher/ascii_exact_match/wall_time

  • 🟥 execution_time [+2.962ns; +2.979ns] or [+11.104%; +11.168%]

scenario:glob_matcher/ascii_exact_miss/wall_time

  • 🟥 execution_time [+2.881ns; +2.946ns] or [+24.873%; +25.429%]

scenario:glob_matcher/ascii_wildcard_question_match/wall_time

  • 🟩 execution_time [-21.267ns; -21.249ns] or [-36.475%; -36.443%]

scenario:glob_matcher/ascii_wildcard_star_match/wall_time

  • 🟩 execution_time [-21.535ns; -21.513ns] or [-36.804%; -36.767%]

scenario:glob_matcher/unicode_pattern_ascii_subject/wall_time

  • 🟥 execution_time [+3.635ns; +3.752ns] or [+4.017%; +4.147%]

Candidate

Omitted due to size.

Baseline

Omitted due to size.

@dd-octo-sts

dd-octo-sts Bot commented Aug 28, 2026

Copy link
Copy Markdown
Contributor

Artifact Size Benchmark Report

aarch64-alpine-linux-musl
Artifact Baseline Commit Change
/aarch64-alpine-linux-musl/lib/libdatadog_profiling.so 8.26 MB 8.26 MB 0% (0 B) 👌
/aarch64-alpine-linux-musl/lib/libdatadog_profiling.a 89.74 MB 89.74 MB 0% (0 B) 👌
aarch64-unknown-linux-gnu
Artifact Baseline Commit Change
/aarch64-unknown-linux-gnu/lib/libdatadog_profiling.a 100.95 MB 100.95 MB 0% (0 B) 👌
/aarch64-unknown-linux-gnu/lib/libdatadog_profiling.so 11.13 MB 11.13 MB 0% (0 B) 👌
libdatadog-x64-windows
Artifact Baseline Commit Change
/libdatadog-x64-windows/debug/dynamic/datadog_profiling_ffi.dll 26.67 MB 26.67 MB 0% (0 B) 👌
/libdatadog-x64-windows/debug/dynamic/datadog_profiling_ffi.lib 94.96 KB 94.96 KB 0% (0 B) 👌
/libdatadog-x64-windows/debug/dynamic/datadog_profiling_ffi.pdb 181.06 MB 181.07 MB +0% (+8.00 KB) 👌
/libdatadog-x64-windows/debug/static/datadog_profiling_ffi.lib 773.75 MB 773.75 MB 0% (0 B) 👌
/libdatadog-x64-windows/release/dynamic/datadog_profiling_ffi.dll 8.75 MB 8.75 MB 0% (0 B) 👌
/libdatadog-x64-windows/release/dynamic/datadog_profiling_ffi.lib 94.96 KB 94.96 KB 0% (0 B) 👌
/libdatadog-x64-windows/release/dynamic/datadog_profiling_ffi.pdb 25.69 MB 25.69 MB 0% (0 B) 👌
/libdatadog-x64-windows/release/static/datadog_profiling_ffi.lib 51.17 MB 51.17 MB 0% (0 B) 👌
libdatadog-x86-windows
Artifact Baseline Commit Change
/libdatadog-x86-windows/debug/dynamic/datadog_profiling_ffi.dll 23.25 MB 23.25 MB 0% (0 B) 👌
/libdatadog-x86-windows/debug/dynamic/datadog_profiling_ffi.lib 96.45 KB 96.45 KB 0% (0 B) 👌
/libdatadog-x86-windows/debug/dynamic/datadog_profiling_ffi.pdb 186.06 MB 186.06 MB 0% (0 B) 👌
/libdatadog-x86-windows/debug/static/datadog_profiling_ffi.lib 760.91 MB 760.91 MB 0% (0 B) 👌
/libdatadog-x86-windows/release/dynamic/datadog_profiling_ffi.dll 6.76 MB 6.76 MB 0% (0 B) 👌
/libdatadog-x86-windows/release/dynamic/datadog_profiling_ffi.lib 96.45 KB 96.45 KB 0% (0 B) 👌
/libdatadog-x86-windows/release/dynamic/datadog_profiling_ffi.pdb 27.62 MB 27.62 MB 0% (0 B) 👌
/libdatadog-x86-windows/release/static/datadog_profiling_ffi.lib 48.69 MB 48.69 MB 0% (0 B) 👌
x86_64-alpine-linux-musl
Artifact Baseline Commit Change
/x86_64-alpine-linux-musl/lib/libdatadog_profiling.a 79.98 MB 79.98 MB 0% (0 B) 👌
/x86_64-alpine-linux-musl/lib/libdatadog_profiling.so 9.17 MB 9.17 MB 0% (0 B) 👌
x86_64-unknown-linux-gnu
Artifact Baseline Commit Change
/x86_64-unknown-linux-gnu/lib/libdatadog_profiling.a 95.70 MB 95.70 MB 0% (0 B) 👌
/x86_64-unknown-linux-gnu/lib/libdatadog_profiling.so 11.19 MB 11.19 MB 0% (0 B) 👌

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