Skip to content

perf(data-pipeline): avoid parsing static entity header names - #2457

Draft
BridgeAR wants to merge 1 commit into
mainfrom
BridgeAR/2026-09-03-wasm-pipeline-size
Draft

perf(data-pipeline): avoid parsing static entity header names#2457
BridgeAR wants to merge 1 commit into
mainfrom
BridgeAR/2026-09-03-wasm-pipeline-size

Conversation

@BridgeAR

@BridgeAR BridgeAR commented Sep 3, 2026

Copy link
Copy Markdown
Member

What does this PR do?

Inserts compile-time entity header names directly while retaining validation for dynamic values.

Motivation

Parsing three known header names on every request adds fallible work and linked code without validating user input.

Additional Notes

The optimized WASM artifact drops from 441,261 to 440,912 bytes.

How to test the change?

Run the data-pipeline-core tests and all-feature Clippy.

@BridgeAR
perf(data-pipeline): avoid parsing static entity header names
7faa90d 
Entity header names are compile-time constants, so parsing them for every request adds code and fallible work without validating dynamic input. Keep value validation and insert the known names directly.

This reduces the optimized WASM artifact from 441,261 to 440,912 bytes with the same Rust and Binaryen toolchain.
@github-actions

github-actions Bot commented Sep 3, 2026

Copy link
Copy Markdown
Contributor

📚 Documentation Check Results

⚠️ 805 documentation warning(s) found

📦 libdd-data-pipeline-core - 805 warning(s)

Updated: 2026-09-03 11:35:15 UTC | Commit: 18e4163 | missing-docs job results

@github-actions

github-actions Bot commented Sep 3, 2026

Copy link
Copy Markdown
Contributor

🔒 Cargo Deny Results

⚠️ 3 issue(s) found, showing only errors (advisories, bans, sources)

📦 libdd-data-pipeline-core - 3 error(s)

Show output 
error[vulnerability]: Invalid pointer dereference in `fmt::Pointer` impl for `Atomic` and `Shared` when the underlying pointer is invalid
   ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:64:1
   │
64 │ crossbeam-epoch 0.9.18 registry+https://github.com/rust-lang/crates.io-index
   │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ security vulnerability detected
   │
   ├ ID: RUSTSEC-2026-0204
   ├ Advisory: https://rustsec.org/advisories/RUSTSEC-2026-0204
   ├ Affected versions of `fmt::Display` dereference the underlying pointer. This causes a invalid pointer dereference e.g., when a pointer created with `Atomic::null` or `Shared::null`. `fmt::Debug` impls and pre-0.9 `fmt::Display` impls, which do not dereference pointers, are not affected by this issue.
   ├ Announcement: https://github.com/crossbeam-rs/crossbeam/pull/1276
   ├ Solution: Upgrade to >=0.9.20 (try `cargo update -p crossbeam-epoch`)
   ├ crossbeam-epoch v0.9.18
     └── crossbeam-deque v0.8.5
         └── rayon-core v1.12.1
             └── rayon v1.10.0
                 └── criterion v0.5.1
                     ├── libdd-common v5.2.0
                     │   ├── libdd-capabilities-impl v4.0.0
                     │   │   └── libdd-trace-utils v11.0.0
                     │   │       ├── libdd-data-pipeline-core v1.0.0
                     │   │       ├── libdd-trace-obfuscation v7.0.0
                     │   │       │   └── libdd-data-pipeline-core v1.0.0 (*)
                     │   │       └── (dev) libdd-trace-utils v11.0.0 (*)
                     │   ├── libdd-data-pipeline-core v1.0.0 (*)
                     │   ├── libdd-trace-obfuscation v7.0.0 (*)
                     │   └── libdd-trace-utils v11.0.0 (*)
                     ├── (dev) libdd-trace-normalization v4.0.0
                     │   └── libdd-trace-utils v11.0.0 (*)
                     ├── (dev) libdd-trace-obfuscation v7.0.0 (*)
                     └── (dev) libdd-trace-utils v11.0.0 (*)

error[vulnerability]: h2 unbounded empty DATA frames
    ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:101:1
    │
101 │ h2 0.4.6 registry+https://github.com/rust-lang/crates.io-index
    │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ security vulnerability detected
    │
    ├ ID: RUSTSEC-2026-0258
    ├ Advisory: https://rustsec.org/advisories/RUSTSEC-2026-0258
    ├ The h2 crate, used internally by hyper, had a flaw that would accept and queue empty DATA frames without limit.
      If streams were not actively drained, this could lead to unbounded memory usage, or a panic if the length overflows.
      
      Low severity.
      
      Patched in v0.4.16.
    ├ Announcement: https://github.com/hyperium/hyper/security/advisories/GHSA-q83h-524g-xf6h
    ├ Solution: Upgrade to >=0.4.16 (try `cargo update -p h2`)
    ├ h2 v0.4.6
      └── hyper v1.6.0
          ├── httpmock v0.8.0-alpha.1
          │   └── libdd-trace-utils v11.0.0
          │       ├── libdd-data-pipeline-core v1.0.0
          │       ├── libdd-trace-obfuscation v7.0.0
          │       │   └── libdd-data-pipeline-core v1.0.0 (*)
          │       └── (dev) libdd-trace-utils v11.0.0 (*)
          ├── hyper-rustls v0.27.7
          │   └── libdd-common v5.2.0
          │       ├── libdd-capabilities-impl v4.0.0
          │       │   └── libdd-trace-utils v11.0.0 (*)
          │       ├── libdd-data-pipeline-core v1.0.0 (*)
          │       ├── libdd-trace-obfuscation v7.0.0 (*)
          │       └── libdd-trace-utils v11.0.0 (*)
          ├── hyper-util v0.1.17
          │   ├── httpmock v0.8.0-alpha.1 (*)
          │   ├── hyper-rustls v0.27.7 (*)
          │   └── libdd-common v5.2.0 (*)
          ├── libdd-common v5.2.0 (*)
          └── libdd-trace-utils v11.0.0 (*)

error[unsound]: Rand is unsound with a custom logger using `rand::rng()`
    ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:192:1
    │
192 │ rand 0.8.5 registry+https://github.com/rust-lang/crates.io-index
    │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ unsound advisory detected
    │
    ├ ID: RUSTSEC-2026-0097
    ├ Advisory: https://rustsec.org/advisories/RUSTSEC-2026-0097
    ├ It has been reported (by [@lopopolo](https://github.com/lopopolo)) that the `rand` library is [unsound](https://rust-lang.github.io/unsafe-code-guidelines/glossary.html#soundness-of-code--of-a-library) (i.e. that safe code using the public API can cause Undefined Behaviour) when all the following conditions are met:
      
      - The `log` and `thread_rng` features are enabled
      - A [custom logger](https://docs.rs/log/latest/log/#implementing-a-logger) is defined
      - The custom logger accesses `rand::rng()` (previously `rand::thread_rng()`) and calls any `TryRng` (previously `RngCore`) methods on `ThreadRng`
      - The `ThreadRng` (attempts to) reseed while called from the custom logger (this happens every 64 kB of generated data)
      - Trace-level logging is enabled or warn-level logging is enabled and the random source (the `getrandom` crate) is unable to provide a new seed
      
      `TryRng` (previously `RngCore`) methods for `ThreadRng` use `unsafe` code to cast `*mut BlockRng<ReseedingCore>` to `&mut BlockRng<ReseedingCore>`. When all the above conditions are met this results in an aliased mutable reference, violating the Stacked Borrows rules. Miri is able to detect this violation in sample code. Since construction of [aliased mutable references is Undefined Behaviour](https://doc.rust-lang.org/stable/nomicon/references.html), the behaviour of optimized builds is hard to predict.
    ├ Announcement: https://github.com/rust-random/rand/pull/1763
    ├ Solution: Upgrade to >=0.10.1 OR <0.10.0, >=0.9.3 OR <0.9.0, >=0.8.6 (try `cargo update -p rand`)
    ├ rand v0.8.5
      ├── (dev) libdd-common v5.2.0
      │   ├── libdd-capabilities-impl v4.0.0
      │   │   └── libdd-trace-utils v11.0.0
      │   │       ├── libdd-data-pipeline-core v1.0.0
      │   │       ├── libdd-trace-obfuscation v7.0.0
      │   │       │   └── libdd-data-pipeline-core v1.0.0 (*)
      │   │       └── (dev) libdd-trace-utils v11.0.0 (*)
      │   ├── libdd-data-pipeline-core v1.0.0 (*)
      │   ├── libdd-trace-obfuscation v7.0.0 (*)
      │   └── libdd-trace-utils v11.0.0 (*)
      ├── (dev) libdd-trace-normalization v4.0.0
      │   └── libdd-trace-utils v11.0.0 (*)
      ├── libdd-trace-utils v11.0.0 (*)
      └── proptest v1.5.0
          ├── (dev) libdd-common v5.2.0 (*)
          └── (dev) libdd-tinybytes v1.1.2
              ├── (dev) libdd-data-pipeline-core v1.0.0 (*)
              ├── (dev) libdd-tinybytes v1.1.2 (*)
              ├── (dev) libdd-trace-obfuscation v7.0.0 (*)
              └── libdd-trace-utils v11.0.0 (*)

advisories FAILED, bans ok, sources ok

Updated: 2026-09-03 11:37:15 UTC | Commit: 18e4163 | dependency-check job results

@datadog-datadog-prod-us1

datadog-datadog-prod-us1 Bot commented Sep 3, 2026

Copy link
Copy Markdown
Contributor

Tests

✅ All CI checks and tests passed.

🎉 All green!

🧪 All tests passed
❄️ No new flaky tests detected

🎯 Code Coverage (details)
• Patch Coverage: 0.00%
• Overall Coverage: 77.04% (-0.04%)

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

@pr-commenter

pr-commenter Bot commented Sep 3, 2026 •
edited
Loading

Copy link
Copy Markdown

Benchmarks

Comparison

Benchmark execution time: 2026-09-03 11:43:40

Comparing candidate commit 7faa90d in PR branch BridgeAR/2026-09-03-wasm-pipeline-size with baseline commit efbbf4c in branch main.

Found 2 performance improvements and 2 performance regressions! Performance is the same for 20 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 ----------------------------------'

scenario:trace_buffer/2_senders/no_delay

  • 🟩 execution_time [-143.505µs; -127.648µs] or [-8.748%; -7.781%]
  • 🟩 throughput [+92716.126op/s; +103790.501op/s] or [+8.442%; +9.450%]

scenario:trace_buffer/4_senders/no_delay

  • 🟥 execution_time [+232.273µs; +247.148µs] or [+6.504%; +6.921%]
  • 🟥 throughput [-65461.667op/s; -61537.286op/s] or [-6.492%; -6.103%]

Candidate

Candidate benchmark details

Group 1

cpu_model git_commit_sha git_commit_date git_branch
Intel(R) Xeon(R) Platinum 8175M CPU @ 2.50GHz 7faa90d 1788404670 BridgeAR/2026-09-03-wasm-pipeline-size
scenario metric min mean ± sd median ± mad p75 p95 p99 max peak_to_median_ratio skewness kurtosis cv sem runs sample_size
trace_buffer/1_senders/10us_delay execution_time 60.044ms 60.086ms ± 0.034ms 60.074ms ± 0.011ms 60.098ms 60.145ms 60.211ms 60.216ms 0.24% 1.922 3.934 0.06% 0.002ms 1 200
trace_buffer/1_senders/10us_delay throughput 14946.082op/s 14978.418op/s ± 8.380op/s 14981.487op/s ± 2.758op/s 14983.054op/s 14986.894op/s 14988.493op/s 14988.995op/s 0.05% -1.918 3.917 0.06% 0.593op/s 1 200
trace_buffer/1_senders/1us_delay execution_time 50.133ms 50.672ms ± 0.205ms 50.630ms ± 0.123ms 50.786ms 51.062ms 51.155ms 51.253ms 1.23% 0.519 0.119 0.40% 0.015ms 1 200
trace_buffer/1_senders/1us_delay throughput 17559.891op/s 17761.624op/s ± 71.738op/s 17775.851op/s ± 43.138op/s 17806.551op/s 17864.420op/s 17883.128op/s 17952.088op/s 0.99% -0.496 0.099 0.40% 5.073op/s 1 200
trace_buffer/1_senders/no_delay execution_time 349.358µs 356.479µs ± 4.284µs 356.199µs ± 1.895µs 358.042µs 361.282µs 370.224µs 384.668µs 7.99% 3.069 17.444 1.20% 0.303µs 1 200
trace_buffer/1_senders/no_delay throughput 2339677.137op/s 2525040.077op/s ± 29326.910op/s 2526678.750op/s ± 13372.638op/s 2540548.277op/s 2561464.889op/s 2573896.768op/s 2576150.586op/s 1.96% -2.727 14.760 1.16% 2073.726op/s 1 200
trace_buffer/2_senders/10us_delay execution_time 60.073ms 60.127ms ± 0.046ms 60.114ms ± 0.020ms 60.141ms 60.224ms 60.296ms 60.328ms 0.36% 1.931 4.272 0.08% 0.003ms 1 200
trace_buffer/2_senders/10us_delay throughput 29837.139op/s 29936.445op/s ± 22.802op/s 29943.094op/s ± 10.155op/s 29950.876op/s 29959.251op/s 29962.800op/s 29963.501op/s 0.07% -1.925 4.243 0.08% 1.612op/s 1 200
trace_buffer/2_senders/1us_delay execution_time 51.046ms 51.234ms ± 0.079ms 51.223ms ± 0.052ms 51.274ms 51.385ms 51.399ms 51.567ms 0.67% 0.740 1.367 0.15% 0.006ms 1 200
trace_buffer/2_senders/1us_delay throughput 34906.219op/s 35133.077op/s ± 54.220op/s 35140.533op/s ± 35.698op/s 35176.222op/s 35201.004op/s 35244.636op/s 35262.467op/s 0.35% -0.727 1.331 0.15% 3.834op/s 1 200
trace_buffer/2_senders/no_delay execution_time 1.428ms 1.505ms ± 0.028ms 1.505ms ± 0.019ms 1.524ms 1.541ms 1.582ms 1.612ms 7.09% 0.050 1.243 1.84% 0.002ms 1 200
trace_buffer/2_senders/no_delay throughput 1116562.798op/s 1196521.615op/s ± 22135.712op/s 1195675.972op/s ± 14860.940op/s 1210458.954op/s 1234504.338op/s 1252862.148op/s 1260576.220op/s 5.43% 0.123 1.062 1.85% 1565.231op/s 1 200
trace_buffer/4_senders/10us_delay execution_time 60.140ms 60.189ms ± 0.045ms 60.177ms ± 0.019ms 60.201ms 60.285ms 60.348ms 60.450ms 0.45% 2.474 8.001 0.07% 0.003ms 1 200
trace_buffer/4_senders/10us_delay throughput 59553.522op/s 59811.132op/s ± 44.790op/s 59823.334op/s ± 18.754op/s 59839.116op/s 59852.943op/s 59859.239op/s 59860.199op/s 0.06% -2.465 7.940 0.07% 3.167op/s 1 200
trace_buffer/4_senders/1us_delay execution_time 51.169ms 51.355ms ± 0.103ms 51.343ms ± 0.060ms 51.408ms 51.561ms 51.675ms 51.775ms 0.84% 1.168 1.899 0.20% 0.007ms 1 200
trace_buffer/4_senders/1us_delay throughput 69531.039op/s 70100.090op/s ± 139.644op/s 70116.042op/s ± 81.572op/s 70192.440op/s 70273.187op/s 70329.662op/s 70355.717op/s 0.34% -1.153 1.847 0.20% 9.874op/s 1 200
trace_buffer/4_senders/no_delay execution_time 3.718ms 3.811ms ± 0.031ms 3.813ms ± 0.020ms 3.830ms 3.859ms 3.880ms 3.891ms 2.04% -0.213 0.220 0.81% 0.002ms 1 200
trace_buffer/4_senders/no_delay throughput 925205.513op/s 944775.771op/s ± 7683.633op/s 944122.983op/s ± 4951.904op/s 949720.370op/s 957432.463op/s 964373.881op/s 968159.702op/s 2.55% 0.266 0.259 0.81% 543.315op/s 1 200
trace_buffer/8_senders/10us_delay execution_time 60.236ms 60.329ms ± 0.059ms 60.316ms ± 0.029ms 60.346ms 60.421ms 60.535ms 60.640ms 0.54% 1.787 4.912 0.10% 0.004ms 1 200
trace_buffer/8_senders/10us_delay throughput 118733.911op/s 119345.963op/s ± 115.916op/s 119371.056op/s ± 56.846op/s 119426.348op/s 119474.727op/s 119497.981op/s 119530.383op/s 0.13% -1.777 4.849 0.10% 8.197op/s 1 200
trace_buffer/8_senders/1us_delay execution_time 51.513ms 51.914ms ± 0.252ms 51.849ms ± 0.126ms 52.038ms 52.406ms 52.611ms 52.622ms 1.49% 0.995 0.087 0.48% 0.018ms 1 200
trace_buffer/8_senders/1us_delay throughput 136825.284op/s 138692.903op/s ± 669.414op/s 138864.366op/s ± 337.844op/s 139177.326op/s 139440.338op/s 139564.724op/s 139771.056op/s 0.65% -0.979 0.053 0.48% 47.335op/s 1 200
trace_buffer/8_senders/no_delay execution_time 7.094ms 7.221ms ± 0.051ms 7.218ms ± 0.031ms 7.251ms 7.308ms 7.347ms 7.358ms 1.94% 0.228 0.045 0.70% 0.004ms 1 200
trace_buffer/8_senders/no_delay throughput 978466.933op/s 997088.848op/s ± 7002.725op/s 997450.967op/s ± 4281.992op/s 1001392.505op/s 1008338.017op/s 1012942.566op/s 1015006.209op/s 1.76% -0.186 0.026 0.70% 495.167op/s 1 200
scenario metric 95% CI mean Shapiro-Wilk pvalue Ljung-Box pvalue (lag=1) Dip test pvalue
trace_buffer/1_senders/10us_delay execution_time [60.082ms; 60.091ms] or [-0.008%; +0.008%] None None None
trace_buffer/1_senders/10us_delay throughput [14977.257op/s; 14979.579op/s] or [-0.008%; +0.008%] None None None
trace_buffer/1_senders/1us_delay execution_time [50.643ms; 50.700ms] or [-0.056%; +0.056%] None None None
trace_buffer/1_senders/1us_delay throughput [17751.681op/s; 17771.566op/s] or [-0.056%; +0.056%] None None None
trace_buffer/1_senders/no_delay execution_time [355.886µs; 357.073µs] or [-0.167%; +0.167%] None None None
trace_buffer/1_senders/no_delay throughput [2520975.649op/s; 2529104.504op/s] or [-0.161%; +0.161%] None None None
trace_buffer/2_senders/10us_delay execution_time [60.121ms; 60.134ms] or [-0.011%; +0.011%] None None None
trace_buffer/2_senders/10us_delay throughput [29933.285op/s; 29939.605op/s] or [-0.011%; +0.011%] None None None
trace_buffer/2_senders/1us_delay execution_time [51.223ms; 51.245ms] or [-0.021%; +0.021%] None None None
trace_buffer/2_senders/1us_delay throughput [35125.563op/s; 35140.592op/s] or [-0.021%; +0.021%] None None None
trace_buffer/2_senders/no_delay execution_time [1.501ms; 1.509ms] or [-0.256%; +0.256%] None None None
trace_buffer/2_senders/no_delay throughput [1193453.818op/s; 1199589.412op/s] or [-0.256%; +0.256%] None None None
trace_buffer/4_senders/10us_delay execution_time [60.183ms; 60.196ms] or [-0.010%; +0.010%] None None None
trace_buffer/4_senders/10us_delay throughput [59804.924op/s; 59817.339op/s] or [-0.010%; +0.010%] None None None
trace_buffer/4_senders/1us_delay execution_time [51.341ms; 51.370ms] or [-0.028%; +0.028%] None None None
trace_buffer/4_senders/1us_delay throughput [70080.737op/s; 70119.443op/s] or [-0.028%; +0.028%] None None None
trace_buffer/4_senders/no_delay execution_time [3.806ms; 3.815ms] or [-0.112%; +0.112%] None None None
trace_buffer/4_senders/no_delay throughput [943710.893op/s; 945840.649op/s] or [-0.113%; +0.113%] None None None
trace_buffer/8_senders/10us_delay execution_time [60.321ms; 60.337ms] or [-0.013%; +0.013%] None None None
trace_buffer/8_senders/10us_delay throughput [119329.898op/s; 119362.028op/s] or [-0.013%; +0.013%] None None None
trace_buffer/8_senders/1us_delay execution_time [51.880ms; 51.949ms] or [-0.067%; +0.067%] None None None
trace_buffer/8_senders/1us_delay throughput [138600.129op/s; 138785.678op/s] or [-0.067%; +0.067%] None None None
trace_buffer/8_senders/no_delay execution_time [7.214ms; 7.228ms] or [-0.097%; +0.097%] None None None
trace_buffer/8_senders/no_delay throughput [996118.337op/s; 998059.358op/s] or [-0.097%; +0.097%] None None None

Baseline

Baseline benchmark details

Group 1

cpu_model git_commit_sha git_commit_date git_branch
Intel(R) Xeon(R) Platinum 8175M CPU @ 2.50GHz efbbf4c 1788373668 main
scenario metric min mean ± sd median ± mad p75 p95 p99 max peak_to_median_ratio skewness kurtosis cv sem runs sample_size
trace_buffer/1_senders/10us_delay execution_time 60.040ms 60.087ms ± 0.038ms 60.072ms ± 0.009ms 60.091ms 60.185ms 60.216ms 60.231ms 0.26% 1.931 3.285 0.06% 0.003ms 1 200
trace_buffer/1_senders/10us_delay throughput 14942.466op/s 14978.320op/s ± 9.532op/s 14981.946op/s ± 2.219op/s 14983.515op/s 14987.018op/s 14989.272op/s 14989.914op/s 0.05% -1.928 3.272 0.06% 0.674op/s 1 200
trace_buffer/1_senders/1us_delay execution_time 50.144ms 50.599ms ± 0.190ms 50.592ms ± 0.145ms 50.743ms 50.916ms 51.042ms 51.103ms 1.01% 0.239 -0.474 0.37% 0.013ms 1 200
trace_buffer/1_senders/1us_delay throughput 17611.504op/s 17787.104op/s ± 66.636op/s 17789.234op/s ± 51.166op/s 17838.993op/s 17884.186op/s 17918.181op/s 17948.439op/s 0.89% -0.222 -0.483 0.37% 4.712op/s 1 200
trace_buffer/1_senders/no_delay execution_time 346.904µs 354.079µs ± 6.778µs 353.645µs ± 2.119µs 355.451µs 361.013µs 377.943µs 422.855µs 19.57% 6.036 53.552 1.91% 0.479µs 1 200
trace_buffer/1_senders/no_delay throughput 2128388.484op/s 2542642.052op/s ± 44023.820op/s 2544927.734op/s ± 15204.910op/s 2565543.459op/s 2584739.227op/s 2592919.326op/s 2594380.727op/s 1.94% -5.066 40.175 1.73% 3112.954op/s 1 200
trace_buffer/2_senders/10us_delay execution_time 60.069ms 60.128ms ± 0.050ms 60.111ms ± 0.023ms 60.145ms 60.235ms 60.275ms 60.394ms 0.47% 1.958 4.808 0.08% 0.004ms 1 200
trace_buffer/2_senders/10us_delay throughput 29804.082op/s 29936.323op/s ± 24.761op/s 29944.752op/s ± 11.307op/s 29952.315op/s 29959.845op/s 29963.034op/s 29965.418op/s 0.07% -1.951 4.762 0.08% 1.751op/s 1 200
trace_buffer/2_senders/1us_delay execution_time 50.928ms 51.220ms ± 0.076ms 51.215ms ± 0.055ms 51.274ms 51.338ms 51.391ms 51.401ms 0.36% -0.109 0.388 0.15% 0.005ms 1 200
trace_buffer/2_senders/1us_delay throughput 35018.862op/s 35142.680op/s ± 52.360op/s 35145.772op/s ± 37.907op/s 35181.971op/s 35226.809op/s 35262.786op/s 35344.264op/s 0.56% 0.120 0.406 0.15% 3.702op/s 1 200
trace_buffer/2_senders/no_delay execution_time 1.522ms 1.640ms ± 0.050ms 1.636ms ± 0.032ms 1.674ms 1.722ms 1.756ms 1.792ms 9.48% 0.281 -0.160 3.04% 0.004ms 1 200
trace_buffer/2_senders/no_delay throughput 1004699.864op/s 1098268.301op/s ± 33261.118op/s 1099968.056op/s ± 21588.843op/s 1118608.898op/s 1156264.562op/s 1164734.968op/s 1182619.366op/s 7.51% -0.123 -0.263 3.02% 2351.916op/s 1 200
trace_buffer/4_senders/10us_delay execution_time 60.137ms 60.201ms ± 0.043ms 60.198ms ± 0.025ms 60.216ms 60.288ms 60.344ms 60.369ms 0.28% 1.400 2.492 0.07% 0.003ms 1 200
trace_buffer/4_senders/10us_delay throughput 59633.328op/s 59799.438op/s ± 42.557op/s 59802.866op/s ± 24.422op/s 59830.039op/s 59849.967op/s 59859.199op/s 59863.111op/s 0.10% -1.394 2.472 0.07% 3.009op/s 1 200
trace_buffer/4_senders/1us_delay execution_time 51.190ms 51.405ms ± 0.152ms 51.362ms ± 0.064ms 51.469ms 51.686ms 51.952ms 52.125ms 1.49% 1.778 4.131 0.29% 0.011ms 1 200
trace_buffer/4_senders/1us_delay throughput 69064.711op/s 70032.178op/s ± 205.352op/s 70090.460op/s ± 87.824op/s 70164.668op/s 70253.065op/s 70291.509op/s 70326.190op/s 0.34% -1.752 3.998 0.29% 14.521op/s 1 200
trace_buffer/4_senders/no_delay execution_time 3.464ms 3.571ms ± 0.044ms 3.569ms ± 0.025ms 3.596ms 3.621ms 3.652ms 3.973ms 11.31% 3.741 33.562 1.23% 0.003ms 1 200
trace_buffer/4_senders/no_delay throughput 906204.967op/s 1008275.247op/s ± 11891.863op/s 1008660.019op/s ± 6983.351op/s 1014858.687op/s 1024193.391op/s 1029942.801op/s 1039293.793op/s 3.04% -3.020 25.660 1.18% 840.882op/s 1 200
trace_buffer/8_senders/10us_delay execution_time 60.251ms 60.338ms ± 0.065ms 60.323ms ± 0.034ms 60.362ms 60.461ms 60.542ms 60.593ms 0.45% 1.379 1.941 0.11% 0.005ms 1 200
trace_buffer/8_senders/10us_delay throughput 118826.501op/s 119328.169op/s ± 127.458op/s 119358.325op/s ± 67.198op/s 119418.255op/s 119464.338op/s 119487.855op/s 119499.451op/s 0.12% -1.372 1.914 0.11% 9.013op/s 1 200
trace_buffer/8_senders/1us_delay execution_time 51.459ms 51.887ms ± 0.262ms 51.811ms ± 0.146ms 52.038ms 52.361ms 52.539ms 52.983ms 2.26% 1.085 1.098 0.50% 0.019ms 1 200
trace_buffer/8_senders/1us_delay throughput 135892.445op/s 138766.483op/s ± 698.019op/s 138965.706op/s ± 392.084op/s 139280.003op/s 139574.651op/s 139714.091op/s 139916.424op/s 0.68% -1.056 0.983 0.50% 49.357op/s 1 200
trace_buffer/8_senders/no_delay execution_time 7.058ms 7.201ms ± 0.063ms 7.195ms ± 0.034ms 7.234ms 7.293ms 7.318ms 7.726ms 7.38% 2.948 22.280 0.88% 0.004ms 1 200
trace_buffer/8_senders/no_delay throughput 931949.239op/s 999948.285op/s ± 8571.466op/s 1000751.583op/s ± 4685.125op/s 1004716.766op/s 1010733.264op/s 1014856.726op/s 1020075.029op/s 1.93% -2.567 18.399 0.86% 606.094op/s 1 200
scenario metric 95% CI mean Shapiro-Wilk pvalue Ljung-Box pvalue (lag=1) Dip test pvalue
trace_buffer/1_senders/10us_delay execution_time [60.082ms; 60.092ms] or [-0.009%; +0.009%] None None None
trace_buffer/1_senders/10us_delay throughput [14976.999op/s; 14979.641op/s] or [-0.009%; +0.009%] None None None
trace_buffer/1_senders/1us_delay execution_time [50.573ms; 50.625ms] or [-0.052%; +0.052%] None None None
trace_buffer/1_senders/1us_delay throughput [17777.869op/s; 17796.339op/s] or [-0.052%; +0.052%] None None None
trace_buffer/1_senders/no_delay execution_time [353.140µs; 355.018µs] or [-0.265%; +0.265%] None None None
trace_buffer/1_senders/no_delay throughput [2536540.774op/s; 2548743.330op/s] or [-0.240%; +0.240%] None None None
trace_buffer/2_senders/10us_delay execution_time [60.121ms; 60.135ms] or [-0.011%; +0.011%] None None None
trace_buffer/2_senders/10us_delay throughput [29932.892op/s; 29939.755op/s] or [-0.011%; +0.011%] None None None
trace_buffer/2_senders/1us_delay execution_time [51.209ms; 51.230ms] or [-0.021%; +0.021%] None None None
trace_buffer/2_senders/1us_delay throughput [35135.423op/s; 35149.936op/s] or [-0.021%; +0.021%] None None None
trace_buffer/2_senders/no_delay execution_time [1.634ms; 1.647ms] or [-0.422%; +0.422%] None None None
trace_buffer/2_senders/no_delay throughput [1093658.630op/s; 1102877.973op/s] or [-0.420%; +0.420%] None None None
trace_buffer/4_senders/10us_delay execution_time [60.195ms; 60.207ms] or [-0.010%; +0.010%] None None None
trace_buffer/4_senders/10us_delay throughput [59793.540op/s; 59805.336op/s] or [-0.010%; +0.010%] None None None
trace_buffer/4_senders/1us_delay execution_time [51.384ms; 51.426ms] or [-0.041%; +0.041%] None None None
trace_buffer/4_senders/1us_delay throughput [70003.719op/s; 70060.638op/s] or [-0.041%; +0.041%] None None None
trace_buffer/4_senders/no_delay execution_time [3.565ms; 3.577ms] or [-0.170%; +0.170%] None None None
trace_buffer/4_senders/no_delay throughput [1006627.150op/s; 1009923.345op/s] or [-0.163%; +0.163%] None None None
trace_buffer/8_senders/10us_delay execution_time [60.329ms; 60.347ms] or [-0.015%; +0.015%] None None None
trace_buffer/8_senders/10us_delay throughput [119310.504op/s; 119345.833op/s] or [-0.015%; +0.015%] None None None
trace_buffer/8_senders/1us_delay execution_time [51.851ms; 51.923ms] or [-0.070%; +0.070%] None None None
trace_buffer/8_senders/1us_delay throughput [138669.744op/s; 138863.221op/s] or [-0.070%; +0.070%] None None None
trace_buffer/8_senders/no_delay execution_time [7.192ms; 7.210ms] or [-0.122%; +0.122%] None None None
trace_buffer/8_senders/no_delay throughput [998760.362op/s; 1001136.208op/s] or [-0.119%; +0.119%] None None None

@dd-octo-sts

dd-octo-sts Bot commented Sep 3, 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.45 MB 8.45 MB 0% (0 B) 👌
/aarch64-alpine-linux-musl/lib/libdatadog_profiling.a 91.30 MB 91.30 MB -0% (-1016 B) 👌
aarch64-unknown-linux-gnu
Artifact Baseline Commit Change
/aarch64-unknown-linux-gnu/lib/libdatadog_profiling.a 102.61 MB 102.61 MB -0% (-976 B) 👌
/aarch64-unknown-linux-gnu/lib/libdatadog_profiling.so 11.38 MB 11.38 MB 0% (0 B) 👌
libdatadog-x64-windows
Artifact Baseline Commit Change
/libdatadog-x64-windows/debug/dynamic/datadog_profiling_ffi.dll 27.33 MB 27.33 MB 0% (0 B) 👌
/libdatadog-x64-windows/debug/dynamic/datadog_profiling_ffi.lib 96.08 KB 96.08 KB 0% (0 B) 👌
/libdatadog-x64-windows/debug/dynamic/datadog_profiling_ffi.pdb 185.41 MB 185.41 MB 0% (0 B) 👌
/libdatadog-x64-windows/debug/static/datadog_profiling_ffi.lib 805.24 MB 805.42 MB +.02% (+188.00 KB) 🔍
/libdatadog-x64-windows/release/dynamic/datadog_profiling_ffi.dll 9.01 MB 9.01 MB -0% (-512 B) 👌
/libdatadog-x64-windows/release/dynamic/datadog_profiling_ffi.lib 96.08 KB 96.08 KB 0% (0 B) 👌
/libdatadog-x64-windows/release/dynamic/datadog_profiling_ffi.pdb 26.21 MB 26.20 MB --.02% (-8.00 KB) 💪
/libdatadog-x64-windows/release/static/datadog_profiling_ffi.lib 52.22 MB 52.22 MB -0% (-956 B) 👌
libdatadog-x86-windows
Artifact Baseline Commit Change
/libdatadog-x86-windows/debug/dynamic/datadog_profiling_ffi.dll 23.82 MB 23.82 MB -0% (-512 B) 👌
/libdatadog-x86-windows/debug/dynamic/datadog_profiling_ffi.lib 97.58 KB 97.58 KB 0% (0 B) 👌
/libdatadog-x86-windows/debug/dynamic/datadog_profiling_ffi.pdb 190.43 MB 190.43 MB 0% (0 B) 👌
/libdatadog-x86-windows/debug/static/datadog_profiling_ffi.lib 788.61 MB 788.67 MB +0% (+54.65 KB) 👌
/libdatadog-x86-windows/release/dynamic/datadog_profiling_ffi.dll 6.96 MB 6.96 MB 0% (0 B) 👌
/libdatadog-x86-windows/release/dynamic/datadog_profiling_ffi.lib 97.58 KB 97.58 KB 0% (0 B) 👌
/libdatadog-x86-windows/release/dynamic/datadog_profiling_ffi.pdb 28.19 MB 28.18 MB --.02% (-8.00 KB) 💪
/libdatadog-x86-windows/release/static/datadog_profiling_ffi.lib 49.70 MB 49.70 MB -0% (-816 B) 👌
x86_64-alpine-linux-musl
Artifact Baseline Commit Change
/x86_64-alpine-linux-musl/lib/libdatadog_profiling.a 81.45 MB 81.45 MB -0% (-1.02 KB) 👌
/x86_64-alpine-linux-musl/lib/libdatadog_profiling.so 9.41 MB 9.41 MB 0% (0 B) 👌
x86_64-unknown-linux-gnu
Artifact Baseline Commit Change
/x86_64-unknown-linux-gnu/lib/libdatadog_profiling.a 97.22 MB 97.22 MB -0% (-992 B) 👌
/x86_64-unknown-linux-gnu/lib/libdatadog_profiling.so 11.46 MB 11.46 MB 0% (0 B) 👌

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@BridgeAR