Skip to content

feat(trace_exporter)!: remove deprecated methods#2250

Open
VianneyRuhlmann wants to merge 1 commit into
mainfrom
vianney/remove-stale-builder-methods
Open

feat(trace_exporter)!: remove deprecated methods#2250
VianneyRuhlmann wants to merge 1 commit into
mainfrom
vianney/remove-stale-builder-methods

Conversation

@VianneyRuhlmann

@VianneyRuhlmann VianneyRuhlmann commented Jul 17, 2026

Copy link
Copy Markdown
Contributor

What does this PR do?

Remove deprecated methods that are doing anything anymore.

Motivation

Clarify public API

Additional Notes

Anything else we should know when reviewing?

How to test the change?

Describe here in detail how the change can be validated.

@VianneyRuhlmann
VianneyRuhlmann marked this pull request as ready for review July 17, 2026 16:21
@VianneyRuhlmann
VianneyRuhlmann requested a review from a team as a code owner July 17, 2026 16:21
@github-actions

github-actions Bot commented Jul 17, 2026

Copy link
Copy Markdown
Contributor

📚 Documentation Check Results

⚠️ 1212 documentation warning(s) found

📦 libdd-data-pipeline - 1212 warning(s)

Updated: 2026-07-17 16:23:22 UTC | Commit: 4ea15c1 | missing-docs job results

@github-actions

github-actions Bot commented Jul 17, 2026

Copy link
Copy Markdown
Contributor

🔒 Cargo Deny Results

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

📦 libdd-data-pipeline - 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:75:1
   │
75 │ 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.1.0
                     │   ├── libdd-capabilities-impl v3.0.0
                     │   │   ├── libdd-data-pipeline v7.0.0
                     │   │   ├── libdd-shared-runtime v2.0.0
                     │   │   │   ├── libdd-data-pipeline v7.0.0 (*)
                     │   │   │   ├── libdd-telemetry v6.0.0
                     │   │   │   │   ├── libdd-data-pipeline v7.0.0 (*)
                     │   │   │   │   └── libdd-trace-stats v6.0.0
                     │   │   │   │       └── libdd-data-pipeline v7.0.0 (*)
                     │   │   │   └── libdd-trace-stats v6.0.0 (*)
                     │   │   ├── libdd-trace-stats v6.0.0 (*)
                     │   │   └── libdd-trace-utils v9.0.0
                     │   │       ├── libdd-data-pipeline v7.0.0 (*)
                     │   │       ├── libdd-trace-obfuscation v5.0.0
                     │   │       │   └── libdd-trace-stats v6.0.0 (*)
                     │   │       ├── libdd-trace-stats v6.0.0 (*)
                     │   │       └── (dev) libdd-trace-utils v9.0.0 (*)
                     │   ├── libdd-data-pipeline v7.0.0 (*)
                     │   ├── libdd-dogstatsd-client v4.0.0
                     │   │   ├── libdd-data-pipeline v7.0.0 (*)
                     │   │   └── libdd-trace-stats v6.0.0 (*)
                     │   ├── libdd-shared-runtime v2.0.0 (*)
                     │   ├── libdd-telemetry v6.0.0 (*)
                     │   ├── libdd-trace-obfuscation v5.0.0 (*)
                     │   ├── libdd-trace-stats v6.0.0 (*)
                     │   └── libdd-trace-utils v9.0.0 (*)
                     ├── (dev) libdd-data-pipeline v7.0.0 (*)
                     ├── (dev) libdd-ddsketch v1.1.0
                     │   ├── libdd-data-pipeline v7.0.0 (*)
                     │   ├── libdd-telemetry v6.0.0 (*)
                     │   └── libdd-trace-stats v6.0.0 (*)
                     ├── (dev) libdd-trace-normalization v3.0.0
                     │   ├── libdd-data-pipeline v7.0.0 (*)
                     │   └── libdd-trace-utils v9.0.0 (*)
                     ├── (dev) libdd-trace-obfuscation v5.0.0 (*)
                     ├── (dev) libdd-trace-stats v6.0.0 (*)
                     └── (dev) libdd-trace-utils v9.0.0 (*)

error[unsound]: Rand is unsound with a custom logger using `rand::rng()`
    ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:218:1
    │
218 │ 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
      ├── libdd-common v5.1.0
      │   ├── libdd-capabilities-impl v3.0.0
      │   │   ├── libdd-data-pipeline v7.0.0
      │   │   ├── libdd-shared-runtime v2.0.0
      │   │   │   ├── libdd-data-pipeline v7.0.0 (*)
      │   │   │   ├── libdd-telemetry v6.0.0
      │   │   │   │   ├── libdd-data-pipeline v7.0.0 (*)
      │   │   │   │   └── libdd-trace-stats v6.0.0
      │   │   │   │       └── libdd-data-pipeline v7.0.0 (*)
      │   │   │   └── libdd-trace-stats v6.0.0 (*)
      │   │   ├── libdd-trace-stats v6.0.0 (*)
      │   │   └── libdd-trace-utils v9.0.0
      │   │       ├── libdd-data-pipeline v7.0.0 (*)
      │   │       ├── libdd-trace-obfuscation v5.0.0
      │   │       │   └── libdd-trace-stats v6.0.0 (*)
      │   │       ├── libdd-trace-stats v6.0.0 (*)
      │   │       └── (dev) libdd-trace-utils v9.0.0 (*)
      │   ├── libdd-data-pipeline v7.0.0 (*)
      │   ├── libdd-dogstatsd-client v4.0.0
      │   │   ├── libdd-data-pipeline v7.0.0 (*)
      │   │   └── libdd-trace-stats v6.0.0 (*)
      │   ├── libdd-shared-runtime v2.0.0 (*)
      │   ├── libdd-telemetry v6.0.0 (*)
      │   ├── libdd-trace-obfuscation v5.0.0 (*)
      │   ├── libdd-trace-stats v6.0.0 (*)
      │   └── libdd-trace-utils v9.0.0 (*)
      ├── (dev) libdd-data-pipeline v7.0.0 (*)
      ├── (dev) libdd-ddsketch v1.1.0
      │   ├── libdd-data-pipeline v7.0.0 (*)
      │   ├── libdd-telemetry v6.0.0 (*)
      │   └── libdd-trace-stats v6.0.0 (*)
      ├── (dev) libdd-trace-normalization v3.0.0
      │   ├── libdd-data-pipeline v7.0.0 (*)
      │   └── libdd-trace-utils v9.0.0 (*)
      ├── (dev) libdd-trace-stats v6.0.0 (*)
      ├── libdd-trace-utils v9.0.0 (*)
      └── proptest v1.5.0
          └── (dev) libdd-tinybytes v1.1.1
              ├── libdd-data-pipeline v7.0.0 (*)
              ├── (dev) libdd-tinybytes v1.1.1 (*)
              └── libdd-trace-utils v9.0.0 (*)

error[vulnerability]: Denial of Service via Stack Exhaustion
    ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:287:1
    │
287 │ time 0.3.41 registry+https://github.com/rust-lang/crates.io-index
    │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ security vulnerability detected
    │
    ├ ID: RUSTSEC-2026-0009
    ├ Advisory: https://rustsec.org/advisories/RUSTSEC-2026-0009
    ├ ## Impact
      
      When user-provided input is provided to any type that parses with the RFC 2822 format, a denial of
      service attack via stack exhaustion is possible. The attack relies on formally deprecated and
      rarely-used features that are part of the RFC 2822 format used in a malicious manner. Ordinary,
      non-malicious input will never encounter this scenario.
      
      ## Patches
      
      A limit to the depth of recursion was added in v0.3.47. From this version, an error will be returned
      rather than exhausting the stack.
      
      ## Workarounds
      
      Limiting the length of user input is the simplest way to avoid stack exhaustion, as the amount of
      the stack consumed would be at most a factor of the length of the input.
    ├ Announcement: https://github.com/time-rs/time/blob/main/CHANGELOG.md#0347-2026-02-05
    ├ Solution: Upgrade to >=0.3.47 (try `cargo update -p time`)
    ├ time v0.3.41
      └── tracing-appender v0.2.3
          └── libdd-log v1.0.0
              └── (dev) libdd-data-pipeline v7.0.0

advisories FAILED, bans ok, sources ok

Updated: 2026-07-17 16:24:42 UTC | Commit: 4ea15c1 | dependency-check job results

@pr-commenter

pr-commenter Bot commented Jul 17, 2026 •
edited
Loading

Copy link
Copy Markdown

Benchmarks

Comparison

Benchmark execution time: 2026-07-17 16:27:02

Comparing candidate commit 192cdfe in PR branch vianney/remove-stale-builder-methods with baseline commit 0c6e2a5 in branch ``.

Found 0 performance improvements and 2 performance regressions! Performance is the same for 22 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 [+70.789µs; +86.761µs] or [+4.349%; +5.330%]
  • 🟥 throughput [-56349.802op/s; -45942.157op/s] or [-5.092%; -4.152%]

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 192cdfe 1784304888 vianney/remove-stale-builder-methods
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 59.985ms 60.076ms ± 0.032ms 60.068ms ± 0.006ms 60.075ms 60.134ms 60.203ms 60.268ms 0.33% 2.777 10.850 0.05% 0.002ms 1 200
trace_buffer/1_senders/10us_delay throughput 14933.177op/s 14981.115op/s ± 7.904op/s 14982.987op/s ± 1.440op/s 14984.299op/s 14988.268op/s 14989.713op/s 15003.803op/s 0.14% -2.769 10.799 0.05% 0.559op/s 1 200
trace_buffer/1_senders/1us_delay execution_time 50.102ms 50.478ms ± 0.161ms 50.455ms ± 0.102ms 50.571ms 50.760ms 50.864ms 50.970ms 1.02% 0.372 -0.051 0.32% 0.011ms 1 200
trace_buffer/1_senders/1us_delay throughput 17657.371op/s 17829.630op/s ± 56.807op/s 17837.798op/s ± 36.041op/s 17865.745op/s 17919.786op/s 17941.524op/s 17963.350op/s 0.70% -0.354 -0.067 0.32% 4.017op/s 1 200
trace_buffer/1_senders/no_delay execution_time 350.446µs 357.150µs ± 3.993µs 356.566µs ± 2.602µs 359.335µs 364.054µs 370.170µs 374.830µs 5.12% 1.359 3.014 1.12% 0.282µs 1 200
trace_buffer/1_senders/no_delay throughput 2401088.662op/s 2520258.560op/s ± 27774.421op/s 2524078.530op/s ± 18551.424op/s 2541924.473op/s 2551836.764op/s 2559237.960op/s 2568157.164op/s 1.75% -1.257 2.558 1.10% 1963.948op/s 1 200
trace_buffer/2_senders/10us_delay execution_time 60.065ms 60.127ms ± 0.037ms 60.122ms ± 0.021ms 60.143ms 60.207ms 60.237ms 60.295ms 0.29% 1.569 3.675 0.06% 0.003ms 1 200
trace_buffer/2_senders/10us_delay throughput 29853.080op/s 29936.426op/s ± 18.165op/s 29939.091op/s ± 10.453op/s 29949.774op/s 29958.672op/s 29961.405op/s 29967.351op/s 0.09% -1.563 3.649 0.06% 1.284op/s 1 200
trace_buffer/2_senders/1us_delay execution_time 50.743ms 51.152ms ± 0.099ms 51.150ms ± 0.062ms 51.214ms 51.309ms 51.375ms 51.456ms 0.60% -0.303 1.608 0.19% 0.007ms 1 200
trace_buffer/2_senders/1us_delay throughput 34981.263op/s 35189.249op/s ± 67.824op/s 35190.296op/s ± 42.634op/s 35228.156op/s 35301.846op/s 35337.403op/s 35472.893op/s 0.80% 0.323 1.650 0.19% 4.796op/s 1 200
trace_buffer/2_senders/no_delay execution_time 1.585ms 1.706ms ± 0.041ms 1.710ms ± 0.028ms 1.734ms 1.771ms 1.787ms 1.807ms 5.70% -0.184 -0.212 2.37% 0.003ms 1 200
trace_buffer/2_senders/no_delay throughput 996060.129op/s 1055424.149op/s ± 25271.513op/s 1052844.942op/s ± 17403.456op/s 1072301.236op/s 1097374.650op/s 1117927.339op/s 1135964.380op/s 7.89% 0.311 -0.095 2.39% 1786.966op/s 1 200
trace_buffer/4_senders/10us_delay execution_time 60.136ms 60.189ms ± 0.034ms 60.183ms ± 0.020ms 60.204ms 60.253ms 60.290ms 60.369ms 0.31% 1.786 5.562 0.06% 0.002ms 1 200
trace_buffer/4_senders/10us_delay throughput 59632.957op/s 59811.766op/s ± 34.210op/s 59817.138op/s ± 19.776op/s 59836.790op/s 59851.907op/s 59857.601op/s 59864.685op/s 0.08% -1.779 5.516 0.06% 2.419op/s 1 200
trace_buffer/4_senders/1us_delay execution_time 51.116ms 51.348ms ± 0.127ms 51.314ms ± 0.060ms 51.385ms 51.609ms 51.756ms 51.987ms 1.31% 1.654 3.871 0.25% 0.009ms 1 200
trace_buffer/4_senders/1us_delay throughput 69248.393op/s 70110.333op/s ± 172.463op/s 70155.615op/s ± 82.142op/s 70214.882op/s 70302.756op/s 70343.482op/s 70427.443op/s 0.39% -1.631 3.755 0.25% 12.195op/s 1 200
trace_buffer/4_senders/no_delay execution_time 3.629ms 3.695ms ± 0.029ms 3.697ms ± 0.022ms 3.716ms 3.740ms 3.758ms 3.765ms 1.85% -0.146 -0.543 0.79% 0.002ms 1 200
trace_buffer/4_senders/no_delay throughput 956084.388op/s 974324.708op/s ± 7748.243op/s 973779.978op/s ± 5711.865op/s 979886.546op/s 987817.384op/s 991465.459op/s 991950.596op/s 1.87% 0.180 -0.543 0.79% 547.884op/s 1 200
trace_buffer/8_senders/10us_delay execution_time 60.232ms 60.311ms ± 0.052ms 60.296ms ± 0.021ms 60.326ms 60.409ms 60.522ms 60.539ms 0.40% 1.857 4.087 0.09% 0.004ms 1 200
trace_buffer/8_senders/10us_delay throughput 118931.168op/s 119380.690op/s ± 103.435op/s 119411.036op/s ± 42.260op/s 119445.061op/s 119481.672op/s 119515.032op/s 119538.333op/s 0.11% -1.850 4.053 0.09% 7.314op/s 1 200
trace_buffer/8_senders/1us_delay execution_time 51.430ms 51.833ms ± 0.252ms 51.742ms ± 0.134ms 51.987ms 52.341ms 52.487ms 52.526ms 1.52% 0.878 -0.096 0.48% 0.018ms 1 200
trace_buffer/8_senders/1us_delay throughput 137074.821op/s 138910.976op/s ± 671.296op/s 139152.765op/s ± 362.361op/s 139389.261op/s 139731.721op/s 139959.256op/s 139997.431op/s 0.61% -0.862 -0.129 0.48% 47.468op/s 1 200
trace_buffer/8_senders/no_delay execution_time 6.969ms 7.120ms ± 0.071ms 7.109ms ± 0.047ms 7.163ms 7.250ms 7.307ms 7.349ms 3.37% 0.709 0.302 0.99% 0.005ms 1 200
trace_buffer/8_senders/no_delay throughput 979700.692op/s 1011351.574op/s ± 9952.847op/s 1012754.157op/s ± 6687.105op/s 1018385.404op/s 1024489.135op/s 1027774.035op/s 1033081.815op/s 2.01% -0.657 0.195 0.98% 703.773op/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.071ms; 60.080ms] or [-0.007%; +0.007%] None None None
trace_buffer/1_senders/10us_delay throughput [14980.020op/s; 14982.211op/s] or [-0.007%; +0.007%] None None None
trace_buffer/1_senders/1us_delay execution_time [50.456ms; 50.501ms] or [-0.044%; +0.044%] None None None
trace_buffer/1_senders/1us_delay throughput [17821.757op/s; 17837.503op/s] or [-0.044%; +0.044%] None None None
trace_buffer/1_senders/no_delay execution_time [356.597µs; 357.703µs] or [-0.155%; +0.155%] None None None
trace_buffer/1_senders/no_delay throughput [2516409.293op/s; 2524107.828op/s] or [-0.153%; +0.153%] None None None
trace_buffer/2_senders/10us_delay execution_time [60.122ms; 60.133ms] or [-0.008%; +0.008%] None None None
trace_buffer/2_senders/10us_delay throughput [29933.908op/s; 29938.943op/s] or [-0.008%; +0.008%] None None None
trace_buffer/2_senders/1us_delay execution_time [51.139ms; 51.166ms] or [-0.027%; +0.027%] None None None
trace_buffer/2_senders/1us_delay throughput [35179.849op/s; 35198.649op/s] or [-0.027%; +0.027%] None None None
trace_buffer/2_senders/no_delay execution_time [1.701ms; 1.712ms] or [-0.330%; +0.330%] None None None
trace_buffer/2_senders/no_delay throughput [1051921.761op/s; 1058926.538op/s] or [-0.332%; +0.332%] None None None
trace_buffer/4_senders/10us_delay execution_time [60.184ms; 60.194ms] or [-0.008%; +0.008%] None None None
trace_buffer/4_senders/10us_delay throughput [59807.025op/s; 59816.507op/s] or [-0.008%; +0.008%] None None None
trace_buffer/4_senders/1us_delay execution_time [51.330ms; 51.366ms] or [-0.034%; +0.034%] None None None
trace_buffer/4_senders/1us_delay throughput [70086.431op/s; 70134.235op/s] or [-0.034%; +0.034%] None None None
trace_buffer/4_senders/no_delay execution_time [3.691ms; 3.699ms] or [-0.110%; +0.110%] None None None
trace_buffer/4_senders/no_delay throughput [973250.877op/s; 975398.540op/s] or [-0.110%; +0.110%] None None None
trace_buffer/8_senders/10us_delay execution_time [60.304ms; 60.319ms] or [-0.012%; +0.012%] None None None
trace_buffer/8_senders/10us_delay throughput [119366.355op/s; 119395.025op/s] or [-0.012%; +0.012%] None None None
trace_buffer/8_senders/1us_delay execution_time [51.798ms; 51.868ms] or [-0.067%; +0.067%] None None None
trace_buffer/8_senders/1us_delay throughput [138817.941op/s; 139004.011op/s] or [-0.067%; +0.067%] None None None
trace_buffer/8_senders/no_delay execution_time [7.110ms; 7.130ms] or [-0.137%; +0.137%] None None None
trace_buffer/8_senders/no_delay throughput [1009972.206op/s; 1012730.943op/s] or [-0.136%; +0.136%] 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 0c6e2a5 1784223782
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.037ms 60.074ms ± 0.027ms 60.069ms ± 0.007ms 60.077ms 60.133ms 60.204ms 60.224ms 0.26% 2.796 10.601 0.04% 0.002ms 1 200
trace_buffer/1_senders/10us_delay throughput 14944.156op/s 14981.459op/s ± 6.602op/s 14982.814op/s ± 1.821op/s 14984.144op/s 14988.843op/s 14990.216op/s 14990.764op/s 0.05% -2.790 10.559 0.04% 0.467op/s 1 200
trace_buffer/1_senders/1us_delay execution_time 50.093ms 50.524ms ± 0.262ms 50.457ms ± 0.154ms 50.666ms 51.106ms 51.273ms 51.315ms 1.70% 1.141 0.894 0.52% 0.019ms 1 200
trace_buffer/1_senders/1us_delay throughput 17538.838op/s 17813.815op/s ± 91.903op/s 17836.870op/s ± 54.223op/s 17879.511op/s 17922.064op/s 17945.500op/s 17966.730op/s 0.73% -1.116 0.830 0.51% 6.499op/s 1 200
trace_buffer/1_senders/no_delay execution_time 345.002µs 353.906µs ± 5.687µs 352.864µs ± 2.415µs 355.603µs 359.513µs 368.679µs 414.023µs 17.33% 6.395 61.896 1.60% 0.402µs 1 200
trace_buffer/1_senders/no_delay throughput 2173794.626op/s 2543647.294op/s ± 37354.779op/s 2550560.201op/s ± 17458.097op/s 2564328.517op/s 2577307.657op/s 2585975.987op/s 2608683.116op/s 2.28% -5.391 47.719 1.46% 2641.382op/s 1 200
trace_buffer/2_senders/10us_delay execution_time 60.069ms 60.121ms ± 0.040ms 60.109ms ± 0.020ms 60.137ms 60.218ms 60.254ms 60.267ms 0.26% 1.657 2.664 0.07% 0.003ms 1 200
trace_buffer/2_senders/10us_delay throughput 29866.873op/s 29939.579op/s ± 19.860op/s 29945.363op/s ± 10.013op/s 29952.224op/s 29959.739op/s 29962.796op/s 29965.338op/s 0.07% -1.653 2.650 0.07% 1.404op/s 1 200
trace_buffer/2_senders/1us_delay execution_time 50.922ms 51.149ms ± 0.101ms 51.157ms ± 0.068ms 51.213ms 51.323ms 51.385ms 51.466ms 0.60% 0.143 -0.114 0.20% 0.007ms 1 200
trace_buffer/2_senders/1us_delay throughput 34974.768op/s 35191.125op/s ± 69.461op/s 35185.831op/s ± 46.762op/s 35235.816op/s 35307.758op/s 35341.720op/s 35348.418op/s 0.46% -0.132 -0.122 0.20% 4.912op/s 1 200
trace_buffer/2_senders/no_delay execution_time 1.511ms 1.628ms ± 0.041ms 1.627ms ± 0.029ms 1.655ms 1.696ms 1.717ms 1.747ms 7.43% 0.090 -0.083 2.50% 0.003ms 1 200
trace_buffer/2_senders/no_delay throughput 1030102.616op/s 1106570.129op/s ± 27770.839op/s 1106624.516op/s ± 19147.285op/s 1125996.001op/s 1151291.012op/s 1169317.815op/s 1191142.663op/s 7.64% 0.054 -0.072 2.50% 1963.695op/s 1 200
trace_buffer/4_senders/10us_delay execution_time 60.132ms 60.185ms ± 0.038ms 60.174ms ± 0.019ms 60.201ms 60.272ms 60.329ms 60.350ms 0.29% 1.759 3.821 0.06% 0.003ms 1 200
trace_buffer/4_senders/10us_delay throughput 59652.202op/s 59815.463op/s ± 37.640op/s 59826.737op/s ± 18.522op/s 59840.450op/s 59855.672op/s 59861.609op/s 59867.826op/s 0.07% -1.754 3.798 0.06% 2.662op/s 1 200
trace_buffer/4_senders/1us_delay execution_time 51.074ms 51.291ms ± 0.152ms 51.251ms ± 0.058ms 51.341ms 51.594ms 51.819ms 52.297ms 2.04% 2.623 10.740 0.30% 0.011ms 1 200
trace_buffer/4_senders/1us_delay throughput 68837.299op/s 70187.740op/s ± 206.993op/s 70243.146op/s ± 78.916op/s 70308.359op/s 70401.784op/s 70436.434op/s 70485.760op/s 0.35% -2.572 10.314 0.29% 14.637op/s 1 200
trace_buffer/4_senders/no_delay execution_time 3.474ms 3.568ms ± 0.034ms 3.567ms ± 0.020ms 3.591ms 3.625ms 3.644ms 3.657ms 2.52% -0.041 -0.009 0.94% 0.002ms 1 200
trace_buffer/4_senders/no_delay throughput 984538.856op/s 1008930.082op/s ± 9494.496op/s 1009325.326op/s ± 5634.478op/s 1014579.222op/s 1024933.797op/s 1031755.826op/s 1036262.032op/s 2.67% 0.097 0.014 0.94% 671.362op/s 1 200
trace_buffer/8_senders/10us_delay execution_time 60.243ms 60.311ms ± 0.047ms 60.296ms ± 0.021ms 60.325ms 60.420ms 60.458ms 60.535ms 0.40% 1.771 3.526 0.08% 0.003ms 1 200
trace_buffer/8_senders/10us_delay throughput 118939.804op/s 119382.197op/s ± 93.382op/s 119411.178op/s ± 42.189op/s 119447.553op/s 119471.449op/s 119490.177op/s 119514.972op/s 0.09% -1.766 3.498 0.08% 6.603op/s 1 200
trace_buffer/8_senders/1us_delay execution_time 51.385ms 51.701ms ± 0.194ms 51.657ms ± 0.119ms 51.821ms 52.093ms 52.239ms 52.317ms 1.28% 0.944 0.364 0.37% 0.014ms 1 200
trace_buffer/8_senders/1us_delay throughput 137622.946op/s 139263.792op/s ± 521.414op/s 139380.510op/s ± 320.250op/s 139656.840op/s 139893.340op/s 139959.361op/s 140117.711op/s 0.53% -0.928 0.321 0.37% 36.870op/s 1 200
trace_buffer/8_senders/no_delay execution_time 6.730ms 7.049ms ± 0.070ms 7.051ms ± 0.035ms 7.095ms 7.137ms 7.200ms 7.227ms 2.49% -1.263 3.951 0.99% 0.005ms 1 200
trace_buffer/8_senders/no_delay throughput 996237.336op/s 1021587.208op/s ± 10275.046op/s 1021075.133op/s ± 5095.028op/s 1025207.724op/s 1038429.145op/s 1062833.585op/s 1069859.921op/s 4.78% 1.395 4.444 1.00% 726.555op/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.071ms; 60.078ms] or [-0.006%; +0.006%] None None None
trace_buffer/1_senders/10us_delay throughput [14980.544op/s; 14982.374op/s] or [-0.006%; +0.006%] None None None
trace_buffer/1_senders/1us_delay execution_time [50.488ms; 50.560ms] or [-0.072%; +0.072%] None None None
trace_buffer/1_senders/1us_delay throughput [17801.078op/s; 17826.552op/s] or [-0.071%; +0.071%] None None None
trace_buffer/1_senders/no_delay execution_time [353.117µs; 354.694µs] or [-0.223%; +0.223%] None None None
trace_buffer/1_senders/no_delay throughput [2538470.281op/s; 2548824.307op/s] or [-0.204%; +0.204%] None None None
trace_buffer/2_senders/10us_delay execution_time [60.116ms; 60.127ms] or [-0.009%; +0.009%] None None None
trace_buffer/2_senders/10us_delay throughput [29936.827op/s; 29942.332op/s] or [-0.009%; +0.009%] None None None
trace_buffer/2_senders/1us_delay execution_time [51.135ms; 51.163ms] or [-0.027%; +0.027%] None None None
trace_buffer/2_senders/1us_delay throughput [35181.498op/s; 35200.751op/s] or [-0.027%; +0.027%] None None None
trace_buffer/2_senders/no_delay execution_time [1.622ms; 1.633ms] or [-0.348%; +0.348%] None None None
trace_buffer/2_senders/no_delay throughput [1102721.358op/s; 1110418.900op/s] or [-0.348%; +0.348%] None None None
trace_buffer/4_senders/10us_delay execution_time [60.180ms; 60.190ms] or [-0.009%; +0.009%] None None None
trace_buffer/4_senders/10us_delay throughput [59810.246op/s; 59820.679op/s] or [-0.009%; +0.009%] None None None
trace_buffer/4_senders/1us_delay execution_time [51.270ms; 51.313ms] or [-0.041%; +0.041%] None None None
trace_buffer/4_senders/1us_delay throughput [70159.053op/s; 70216.427op/s] or [-0.041%; +0.041%] None None None
trace_buffer/4_senders/no_delay execution_time [3.564ms; 3.573ms] or [-0.130%; +0.130%] None None None
trace_buffer/4_senders/no_delay throughput [1007614.236op/s; 1010245.928op/s] or [-0.130%; +0.130%] None None None
trace_buffer/8_senders/10us_delay execution_time [60.304ms; 60.317ms] or [-0.011%; +0.011%] None None None
trace_buffer/8_senders/10us_delay throughput [119369.255op/s; 119395.139op/s] or [-0.011%; +0.011%] None None None
trace_buffer/8_senders/1us_delay execution_time [51.674ms; 51.728ms] or [-0.052%; +0.052%] None None None
trace_buffer/8_senders/1us_delay throughput [139191.529op/s; 139336.055op/s] or [-0.052%; +0.052%] None None None
trace_buffer/8_senders/no_delay execution_time [7.039ms; 7.058ms] or [-0.138%; +0.138%] None None None
trace_buffer/8_senders/no_delay throughput [1020163.185op/s; 1023011.230op/s] or [-0.139%; +0.139%] None None None

@datadog-datadog-us1-prod

datadog-datadog-us1-prod Bot commented Jul 17, 2026

Copy link
Copy Markdown

Tests

🎉 All green!

🧪 All tests passed
❄️ No new flaky tests detected

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

This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 192cdfe | Docs | Datadog PR Page | Give us feedback!

@dd-octo-sts

dd-octo-sts Bot commented Jul 17, 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 7.88 MB 7.88 MB 0% (0 B) 👌
/aarch64-alpine-linux-musl/lib/libdatadog_profiling.a 85.88 MB 85.88 MB +0% (+632 B) 👌
aarch64-unknown-linux-gnu
Artifact Baseline Commit Change
/aarch64-unknown-linux-gnu/lib/libdatadog_profiling.a 97.10 MB 97.10 MB +0% (+416 B) 👌
/aarch64-unknown-linux-gnu/lib/libdatadog_profiling.so 10.61 MB 10.61 MB 0% (0 B) 👌
libdatadog-x64-windows
Artifact Baseline Commit Change
/libdatadog-x64-windows/debug/dynamic/datadog_profiling_ffi.dll 25.45 MB 25.45 MB 0% (0 B) 👌
/libdatadog-x64-windows/debug/dynamic/datadog_profiling_ffi.lib 88.44 KB 88.44 KB 0% (0 B) 👌
/libdatadog-x64-windows/debug/dynamic/datadog_profiling_ffi.pdb 184.55 MB 184.55 MB -0% (-8.00 KB) 👌
/libdatadog-x64-windows/debug/static/datadog_profiling_ffi.lib 946.77 MB 946.76 MB -0% (-1.32 KB) 👌
/libdatadog-x64-windows/release/dynamic/datadog_profiling_ffi.dll 8.32 MB 8.32 MB 0% (0 B) 👌
/libdatadog-x64-windows/release/dynamic/datadog_profiling_ffi.lib 88.44 KB 88.44 KB 0% (0 B) 👌
/libdatadog-x64-windows/release/dynamic/datadog_profiling_ffi.pdb 24.62 MB 24.62 MB 0% (0 B) 👌
/libdatadog-x64-windows/release/static/datadog_profiling_ffi.lib 49.03 MB 49.03 MB -0% (-4 B) 👌
libdatadog-x86-windows
Artifact Baseline Commit Change
/libdatadog-x86-windows/debug/dynamic/datadog_profiling_ffi.dll 22.05 MB 22.05 MB 0% (0 B) 👌
/libdatadog-x86-windows/debug/dynamic/datadog_profiling_ffi.lib 89.82 KB 89.82 KB 0% (0 B) 👌
/libdatadog-x86-windows/debug/dynamic/datadog_profiling_ffi.pdb 188.76 MB 188.76 MB 0% (0 B) 👌
/libdatadog-x86-windows/debug/static/datadog_profiling_ffi.lib 935.45 MB 935.44 MB -0% (-1.32 KB) 👌
/libdatadog-x86-windows/release/dynamic/datadog_profiling_ffi.dll 6.43 MB 6.43 MB 0% (0 B) 👌
/libdatadog-x86-windows/release/dynamic/datadog_profiling_ffi.lib 89.82 KB 89.82 KB 0% (0 B) 👌
/libdatadog-x86-windows/release/dynamic/datadog_profiling_ffi.pdb 26.43 MB 26.43 MB 0% (0 B) 👌
/libdatadog-x86-windows/release/static/datadog_profiling_ffi.lib 46.66 MB 46.66 MB -0% (-6 B) 👌
x86_64-alpine-linux-musl
Artifact Baseline Commit Change
/x86_64-alpine-linux-musl/lib/libdatadog_profiling.a 76.58 MB 76.58 MB -0% (-16 B) 👌
/x86_64-alpine-linux-musl/lib/libdatadog_profiling.so 8.78 MB 8.78 MB 0% (0 B) 👌
x86_64-unknown-linux-gnu
Artifact Baseline Commit Change
/x86_64-unknown-linux-gnu/lib/libdatadog_profiling.a 92.10 MB 92.10 MB 0% (0 B) 👌
/x86_64-unknown-linux-gnu/lib/libdatadog_profiling.so 10.69 MB 10.69 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

data-pipeline

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@VianneyRuhlmann