Skip to content

chore(deps): bump libdd-ffe-test-suite/ffe-system-test-data from ea8b5cc to c67dbd6 - #2388

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/submodules/libdd-ffe-test-suite/ffe-system-test-data-c67dbd6
Open

chore(deps): bump libdd-ffe-test-suite/ffe-system-test-data from ea8b5cc to c67dbd6#2388
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/submodules/libdd-ffe-test-suite/ffe-system-test-data-c67dbd6

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Aug 20, 2026

Copy link
Copy Markdown
Contributor

Bumps libdd-ffe-test-suite/ffe-system-test-data from ea8b5cc to c67dbd6.

Commits
  • c67dbd6 Merge pull request #29 from greghuels/greg.huels/semver-fix
  • 8b2c2a0 test: address semver review feedback
  • b647031 Merge pull request #21 from DataDog/blake.thomas/FFL-2914-pr0-regex-conforman...
  • 85ba45e test: promote SEMVER_* unit-test coverage into shared system tests
  • 8e8a6c2 Version narrowed regex contract
  • 6c11ed1 Narrow portable regex authoring contract
  • 3160ea4 Clarify targeting regex contract scope
  • 6788ce9 test: reject invalid SemVer comparand in a waterfall at parse time
  • ab0a81f ci: keep existing downstream drift advisory
  • 2c55e32 Merge latest main into regex conformance fixture
  • Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [libdd-ffe-test-suite/ffe-system-test-data](https://github.com/DataDog/ffe-system-test-data) from `ea8b5cc` to `c67dbd6`.
- [Commits](DataDog/ffe-system-test-data@ea8b5cc...c67dbd6)

---
updated-dependencies:
- dependency-name: libdd-ffe-test-suite/ffe-system-test-data
  dependency-version: c67dbd6dc1dc505f4e85504124658cb739c9c380
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file submodules Pull requests that update submodules code labels Aug 20, 2026
@dependabot
dependabot Bot requested a review from a team as a code owner August 20, 2026 22:43
@dependabot
dependabot Bot removed the request for review from a team August 20, 2026 22:43
@dependabot dependabot Bot added the dependencies Pull requests that update a dependency file label Aug 20, 2026
@dependabot dependabot Bot added the submodules Pull requests that update submodules code label Aug 20, 2026
@github-actions

github-actions Bot commented Aug 20, 2026

Copy link
Copy Markdown
Contributor

📚 Documentation Check Results

No documentation warnings found!

📦 libdd-ffe-test-suite - ✅ No warnings


Updated: 2026-08-20 22:45:04 UTC | Commit: e83b0cc | missing-docs job results

@github-actions

github-actions Bot commented Aug 20, 2026

Copy link
Copy Markdown
Contributor

🔒 Cargo Deny Results

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

📦 libdd-ffe-test-suite - 5 error(s)

Show output
error[unmaintained]: Bincode is unmaintained
   ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:24:1
   │
24 │ bincode 1.3.3 registry+https://github.com/rust-lang/crates.io-index
   │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ unmaintained advisory detected
   │
   ├ ID: RUSTSEC-2025-0141
   ├ Advisory: https://rustsec.org/advisories/RUSTSEC-2025-0141
   ├ Due to a doxxing and harassment incident, the bincode team has taken the decision to cease development permanently.
     
     The team considers version 1.3.3 a complete version of bincode that is not in need of any updates.
     
     ## Alternatives to consider
     
     * [wincode](https://crates.io/crates/wincode)
     * [postcard](https://crates.io/crates/postcard)
     * [bitcode](https://crates.io/crates/bitcode)
     * [rkyv](https://crates.io/crates/rkyv)
   ├ Announcement: https://git.sr.ht/~stygianentity/bincode/tree/v3.0/item/README.md
   ├ Solution: No safe upgrade is available!
   ├ bincode v1.3.3
     └── (dev) libdd-ffe v1.0.0
         └── (dev) libdd-ffe-test-suite v41.0.0

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:55:1
   │
55 │ 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
                     └── (dev) libdd-ffe-test-suite v41.0.0

error[vulnerability]: h2 unbounded empty DATA frames
   ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:97:1
   │
97 │ 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
         │   └── (dev) libdd-ffe v1.0.0
         │       └── (dev) libdd-ffe-test-suite v41.0.0
         ├── hyper-rustls v0.27.7
         │   └── libdd-common v5.2.0
         │       ├── libdd-capabilities-impl v4.0.0
         │       │   ├── (dev) libdd-ffe v1.0.0 (*)
         │       │   └── libdd-remote-config v3.0.0
         │       │       ├── libdd-ffe v1.0.0 (*)
         │       │       └── (dev) libdd-remote-config v3.0.0 (*)
         │       ├── libdd-ffe v1.0.0 (*)
         │       └── libdd-remote-config v3.0.0 (*)
         ├── hyper-util v0.1.17
         │   ├── httpmock v0.8.0-alpha.1 (*)
         │   ├── hyper-rustls v0.27.7 (*)
         │   ├── libdd-common v5.2.0 (*)
         │   └── libdd-remote-config v3.0.0 (*)
         ├── libdd-common v5.2.0 (*)
         └── libdd-remote-config v3.0.0 (*)

error[unsound]: Rand is unsound with a custom logger using `rand::rng()`
    ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:185:1
    │
185 │ 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
      │   │   ├── (dev) libdd-ffe v1.0.0
      │   │   │   └── (dev) libdd-ffe-test-suite v41.0.0
      │   │   └── libdd-remote-config v3.0.0
      │   │       ├── libdd-ffe v1.0.0 (*)
      │   │       └── (dev) libdd-remote-config v3.0.0 (*)
      │   ├── libdd-ffe v1.0.0 (*)
      │   └── libdd-remote-config v3.0.0 (*)
      └── proptest v1.5.0
          └── (dev) libdd-common v5.2.0 (*)

error[vulnerability]: Denial of Service via Stack Exhaustion
    ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:249:1
    │
249 │ 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
      └── libdd-remote-config v3.0.0
          ├── libdd-ffe v1.0.0
          │   └── (dev) libdd-ffe-test-suite v41.0.0
          └── (dev) libdd-remote-config v3.0.0 (*)

advisories FAILED, bans ok, sources ok

Updated: 2026-08-20 22:47:09 UTC | Commit: e83b0cc | dependency-check job results

@datadog-prod-us1-4

datadog-prod-us1-4 Bot commented Aug 20, 2026

Copy link
Copy Markdown

Pipelines

⚠️ Warnings

🚦 5 Pipeline jobs failed

Required checks pass | allchecks

View in Datadog · View in GitHub Actions

Job did not run: blocked by a failed job in an earlier pipeline stage.

Test | Test x86_64-unknown-linux-gnu on centOS7 docker image

View in Datadog · View in GitHub Actions

API key is missing. Ensure 'DATADOG_API_KEY' or 'DD_API_KEY' is set in your environment.

Test | cargo test #macos-15

View in Datadog · View in GitHub Actions

Internal Error: API key is missing

View all 5 failed jobs.

Useful? React with 👍 / 👎

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

@pr-commenter

pr-commenter Bot commented Aug 20, 2026

Copy link
Copy Markdown

Benchmarks

Comparison

Benchmark execution time: 2026-08-20 22:55:24

Comparing candidate commit fbf71ab in PR branch dependabot/submodules/libdd-ffe-test-suite/ffe-system-test-data-c67dbd6 with baseline commit 378be45 in branch main.

Found 0 performance improvements and 1 performance regressions! Performance is the same for 13 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:sdk_test_data/rules-based

  • 🟥 execution_time [+22.726µs; +25.169µs] or [+15.520%; +17.188%]

Candidate

Candidate benchmark details

Group 1

cpu_model git_commit_sha git_commit_date git_branch
Intel(R) Xeon(R) Platinum 8259CL CPU @ 2.50GHz fbf71ab 1787265792 dependabot/submodules/libdd-ffe-test-suite/ffe-system-test-data-c67dbd6
scenario metric min mean ± sd median ± mad p75 p95 p99 max peak_to_median_ratio skewness kurtosis cv sem runs sample_size
single_flag_killswitch/rules-based execution_time 156.458ns 160.600ns ± 3.512ns 160.033ns ± 1.951ns 161.962ns 167.815ns 172.738ns 178.321ns 11.43% 1.737 4.181 2.18% 0.248ns 1 200
scenario metric 95% CI mean Shapiro-Wilk pvalue Ljung-Box pvalue (lag=1) Dip test pvalue
single_flag_killswitch/rules-based execution_time [160.113ns; 161.087ns] or [-0.303%; +0.303%] None None None

Group 2

cpu_model git_commit_sha git_commit_date git_branch
Intel(R) Xeon(R) Platinum 8259CL CPU @ 2.50GHz fbf71ab 1787265792 dependabot/submodules/libdd-ffe-test-suite/ffe-system-test-data-c67dbd6
scenario metric min mean ± sd median ± mad p75 p95 p99 max peak_to_median_ratio skewness kurtosis cv sem runs sample_size
sdk_test_data/rules-based execution_time 166.988µs 170.383µs ± 6.560µs 169.022µs ± 0.880µs 170.142µs 176.635µs 195.825µs 240.381µs 42.22% 7.456 68.353 3.84% 0.464µs 1 200
scenario metric 95% CI mean Shapiro-Wilk pvalue Ljung-Box pvalue (lag=1) Dip test pvalue
sdk_test_data/rules-based execution_time [169.474µs; 171.292µs] or [-0.534%; +0.534%] None None None

Group 3

cpu_model git_commit_sha git_commit_date git_branch
Intel(R) Xeon(R) Platinum 8259CL CPU @ 2.50GHz fbf71ab 1787265792 dependabot/submodules/libdd-ffe-test-suite/ffe-system-test-data-c67dbd6
scenario metric min mean ± sd median ± mad p75 p95 p99 max peak_to_median_ratio skewness kurtosis cv sem runs sample_size
flagevaluation_evp/coalescer/scale/2500flags_500users_20fields execution_time 5.323ms 5.338ms ± 0.007ms 5.337ms ± 0.004ms 5.342ms 5.349ms 5.352ms 5.372ms 0.67% 0.964 3.358 0.13% 0.000ms 1 200
flagevaluation_evp/coalescer/scale/2500flags_500users_20fields throughput 465343.886op/s 468373.980op/s ± 590.336op/s 468460.016op/s ± 365.151op/s 468731.628op/s 469265.662op/s 469402.019op/s 469693.651op/s 0.26% -0.947 3.278 0.13% 41.743op/s 1 200
flagevaluation_evp/coalescer/stress/10flags_1000users_250fields execution_time 7.932ms 7.947ms ± 0.007ms 7.946ms ± 0.003ms 7.950ms 7.956ms 7.982ms 7.989ms 0.53% 2.334 11.451 0.09% 0.001ms 1 200
flagevaluation_evp/coalescer/stress/10flags_1000users_250fields throughput 125176.703op/s 125837.533op/s ± 114.388op/s 125845.675op/s ± 54.741op/s 125896.601op/s 125994.845op/s 126055.226op/s 126077.384op/s 0.18% -2.313 11.315 0.09% 8.088op/s 1 200
flagevaluation_evp/coalescer/typical/100flags_50users_10fields execution_time 171.620µs 184.148µs ± 38.443µs 181.513µs ± 0.259µs 181.838µs 182.503µs 182.888µs 724.782µs 299.30% 14.011 194.544 20.82% 2.718µs 1 200
flagevaluation_evp/coalescer/typical/100flags_50users_10fields throughput 137972.521op/s 549135.751op/s ± 29514.398op/s 550924.975op/s ± 787.388op/s 551615.464op/s 552272.839op/s 576453.251op/s 582683.803op/s 5.76% -13.599 187.237 5.36% 2086.983op/s 1 200
scenario metric 95% CI mean Shapiro-Wilk pvalue Ljung-Box pvalue (lag=1) Dip test pvalue
flagevaluation_evp/coalescer/scale/2500flags_500users_20fields execution_time [5.337ms; 5.339ms] or [-0.017%; +0.017%] None None None
flagevaluation_evp/coalescer/scale/2500flags_500users_20fields throughput [468292.165op/s; 468455.795op/s] or [-0.017%; +0.017%] None None None
flagevaluation_evp/coalescer/stress/10flags_1000users_250fields execution_time [7.946ms; 7.948ms] or [-0.013%; +0.013%] None None None
flagevaluation_evp/coalescer/stress/10flags_1000users_250fields throughput [125821.680op/s; 125853.386op/s] or [-0.013%; +0.013%] None None None
flagevaluation_evp/coalescer/typical/100flags_50users_10fields execution_time [178.821µs; 189.476µs] or [-2.893%; +2.893%] None None None
flagevaluation_evp/coalescer/typical/100flags_50users_10fields throughput [545045.339op/s; 553226.163op/s] or [-0.745%; +0.745%] None None None

Group 4

cpu_model git_commit_sha git_commit_date git_branch
Intel(R) Xeon(R) Platinum 8259CL CPU @ 2.50GHz fbf71ab 1787265792 dependabot/submodules/libdd-ffe-test-suite/ffe-system-test-data-c67dbd6
scenario metric min mean ± sd median ± mad p75 p95 p99 max peak_to_median_ratio skewness kurtosis cv sem runs sample_size
flagevaluation_evp/payloads/scale/2500flags_500users_20fields execution_time 21.842ms 21.908ms ± 0.027ms 21.909ms ± 0.019ms 21.925ms 21.952ms 21.967ms 21.977ms 0.31% 0.030 -0.419 0.12% 0.002ms 1 200
flagevaluation_evp/payloads/scale/2500flags_500users_20fields throughput 113754.593op/s 114113.652op/s ± 138.708op/s 114109.059op/s ± 97.662op/s 114219.282op/s 114326.704op/s 114436.658op/s 114457.026op/s 0.30% -0.024 -0.419 0.12% 9.808op/s 1 200
flagevaluation_evp/payloads/stress/10flags_1000users_250fields execution_time 102.584ms 103.105ms ± 0.288ms 103.067ms ± 0.149ms 103.218ms 103.547ms 103.755ms 105.365ms 2.23% 2.700 17.548 0.28% 0.020ms 1 200
flagevaluation_evp/payloads/stress/10flags_1000users_250fields throughput 9490.773op/s 9698.881op/s ± 26.911op/s 9702.425op/s ± 14.014op/s 9715.539op/s 9732.395op/s 9741.405op/s 9748.101op/s 0.47% -2.599 16.539 0.28% 1.903op/s 1 200
flagevaluation_evp/payloads/typical/100flags_50users_10fields execution_time 597.637µs 600.077µs ± 0.954µs 600.063µs ± 0.529µs 600.576µs 601.795µs 602.697µs 602.996µs 0.49% 0.302 0.862 0.16% 0.067µs 1 200
flagevaluation_evp/payloads/typical/100flags_50users_10fields throughput 165838.593op/s 166645.649op/s ± 264.830op/s 166649.280op/s ± 146.918op/s 166800.665op/s 167086.526op/s 167254.012op/s 167325.514op/s 0.41% -0.289 0.851 0.16% 18.726op/s 1 200
scenario metric 95% CI mean Shapiro-Wilk pvalue Ljung-Box pvalue (lag=1) Dip test pvalue
flagevaluation_evp/payloads/scale/2500flags_500users_20fields execution_time [21.904ms; 21.912ms] or [-0.017%; +0.017%] None None None
flagevaluation_evp/payloads/scale/2500flags_500users_20fields throughput [114094.428op/s; 114132.876op/s] or [-0.017%; +0.017%] None None None
flagevaluation_evp/payloads/stress/10flags_1000users_250fields execution_time [103.066ms; 103.145ms] or [-0.039%; +0.039%] None None None
flagevaluation_evp/payloads/stress/10flags_1000users_250fields throughput [9695.151op/s; 9702.610op/s] or [-0.038%; +0.038%] None None None
flagevaluation_evp/payloads/typical/100flags_50users_10fields execution_time [599.945µs; 600.209µs] or [-0.022%; +0.022%] None None None
flagevaluation_evp/payloads/typical/100flags_50users_10fields throughput [166608.946op/s; 166682.352op/s] or [-0.022%; +0.022%] None None None

Baseline

Baseline benchmark details

Group 1

cpu_model git_commit_sha git_commit_date git_branch
Intel(R) Xeon(R) Platinum 8259CL CPU @ 2.50GHz 378be45 1787251662 main
scenario metric min mean ± sd median ± mad p75 p95 p99 max peak_to_median_ratio skewness kurtosis cv sem runs sample_size
single_flag_killswitch/rules-based execution_time 156.586ns 160.122ns ± 2.909ns 159.439ns ± 1.511ns 160.973ns 166.098ns 170.082ns 173.856ns 9.04% 1.705 3.509 1.81% 0.206ns 1 200
scenario metric 95% CI mean Shapiro-Wilk pvalue Ljung-Box pvalue (lag=1) Dip test pvalue
single_flag_killswitch/rules-based execution_time [159.719ns; 160.525ns] or [-0.252%; +0.252%] None None None

Group 2

cpu_model git_commit_sha git_commit_date git_branch
Intel(R) Xeon(R) Platinum 8259CL CPU @ 2.50GHz 378be45 1787251662 main
scenario metric min mean ± sd median ± mad p75 p95 p99 max peak_to_median_ratio skewness kurtosis cv sem runs sample_size
sdk_test_data/rules-based execution_time 143.021µs 146.435µs ± 5.886µs 145.263µs ± 0.781µs 146.105µs 151.228µs 168.220µs 209.416µs 44.16% 7.600 70.156 4.01% 0.416µs 1 200
scenario metric 95% CI mean Shapiro-Wilk pvalue Ljung-Box pvalue (lag=1) Dip test pvalue
sdk_test_data/rules-based execution_time [145.619µs; 147.251µs] or [-0.557%; +0.557%] None None None

Group 3

cpu_model git_commit_sha git_commit_date git_branch
Intel(R) Xeon(R) Platinum 8259CL CPU @ 2.50GHz 378be45 1787251662 main
scenario metric min mean ± sd median ± mad p75 p95 p99 max peak_to_median_ratio skewness kurtosis cv sem runs sample_size
flagevaluation_evp/coalescer/scale/2500flags_500users_20fields execution_time 5.323ms 5.339ms ± 0.008ms 5.339ms ± 0.006ms 5.345ms 5.352ms 5.358ms 5.365ms 0.49% 0.367 0.189 0.15% 0.001ms 1 200
flagevaluation_evp/coalescer/scale/2500flags_500users_20fields throughput 465959.948op/s 468246.486op/s ± 693.640op/s 468259.718op/s ± 532.114op/s 468764.741op/s 469317.871op/s 469514.667op/s 469631.381op/s 0.29% -0.358 0.171 0.15% 49.048op/s 1 200
flagevaluation_evp/coalescer/stress/10flags_1000users_250fields execution_time 7.940ms 7.957ms ± 0.008ms 7.956ms ± 0.004ms 7.959ms 7.966ms 7.994ms 8.003ms 0.59% 2.459 10.094 0.10% 0.001ms 1 200
flagevaluation_evp/coalescer/stress/10flags_1000users_250fields throughput 124956.135op/s 125680.478op/s ± 130.571op/s 125694.238op/s ± 59.921op/s 125755.838op/s 125838.058op/s 125915.891op/s 125949.951op/s 0.20% -2.441 9.989 0.10% 9.233op/s 1 200
flagevaluation_evp/coalescer/typical/100flags_50users_10fields execution_time 179.651µs 181.646µs ± 0.445µs 181.590µs ± 0.200µs 181.878µs 182.364µs 182.500µs 183.826µs 1.23% -0.432 5.611 0.24% 0.031µs 1 200
flagevaluation_evp/coalescer/typical/100flags_50users_10fields throughput 543992.689op/s 550525.102op/s ± 1351.505op/s 550692.391op/s ± 604.350op/s 551044.625op/s 552859.446op/s 554175.899op/s 556633.569op/s 1.08% 0.487 5.607 0.24% 95.566op/s 1 200
scenario metric 95% CI mean Shapiro-Wilk pvalue Ljung-Box pvalue (lag=1) Dip test pvalue
flagevaluation_evp/coalescer/scale/2500flags_500users_20fields execution_time [5.338ms; 5.340ms] or [-0.021%; +0.021%] None None None
flagevaluation_evp/coalescer/scale/2500flags_500users_20fields throughput [468150.355op/s; 468342.618op/s] or [-0.021%; +0.021%] None None None
flagevaluation_evp/coalescer/stress/10flags_1000users_250fields execution_time [7.956ms; 7.958ms] or [-0.014%; +0.014%] None None None
flagevaluation_evp/coalescer/stress/10flags_1000users_250fields throughput [125662.382op/s; 125698.574op/s] or [-0.014%; +0.014%] None None None
flagevaluation_evp/coalescer/typical/100flags_50users_10fields execution_time [181.584µs; 181.708µs] or [-0.034%; +0.034%] None None None
flagevaluation_evp/coalescer/typical/100flags_50users_10fields throughput [550337.796op/s; 550712.408op/s] or [-0.034%; +0.034%] None None None

Group 4

cpu_model git_commit_sha git_commit_date git_branch
Intel(R) Xeon(R) Platinum 8259CL CPU @ 2.50GHz 378be45 1787251662 main
scenario metric min mean ± sd median ± mad p75 p95 p99 max peak_to_median_ratio skewness kurtosis cv sem runs sample_size
flagevaluation_evp/payloads/scale/2500flags_500users_20fields execution_time 21.983ms 22.113ms ± 0.059ms 22.119ms ± 0.038ms 22.150ms 22.205ms 22.255ms 22.275ms 0.71% 0.134 -0.346 0.27% 0.004ms 1 200
flagevaluation_evp/payloads/scale/2500flags_500users_20fields throughput 112234.310op/s 113056.196op/s ± 302.681op/s 113027.320op/s ± 195.338op/s 113247.155op/s 113550.122op/s 113583.097op/s 113726.569op/s 0.62% -0.121 -0.358 0.27% 21.403op/s 1 200
flagevaluation_evp/payloads/stress/10flags_1000users_250fields execution_time 103.224ms 103.671ms ± 0.250ms 103.683ms ± 0.053ms 103.723ms 103.774ms 103.828ms 106.933ms 3.13% 11.077 142.946 0.24% 0.018ms 1 200
flagevaluation_evp/payloads/stress/10flags_1000users_250fields throughput 9351.659op/s 9645.993op/s ± 22.685op/s 9644.765op/s ± 4.963op/s 9654.694op/s 9661.703op/s 9665.263op/s 9687.649op/s 0.44% -10.916 140.262 0.23% 1.604op/s 1 200
flagevaluation_evp/payloads/typical/100flags_50users_10fields execution_time 598.592µs 600.122µs ± 0.665µs 600.098µs ± 0.414µs 600.572µs 601.017µs 601.153µs 605.110µs 0.84% 1.984 14.221 0.11% 0.047µs 1 200
flagevaluation_evp/payloads/typical/100flags_50users_10fields throughput 165259.129op/s 166633.098op/s ± 184.282op/s 166639.547op/s ± 114.949op/s 166752.170op/s 166888.933op/s 166976.746op/s 167058.793op/s 0.25% -1.944 13.858 0.11% 13.031op/s 1 200
scenario metric 95% CI mean Shapiro-Wilk pvalue Ljung-Box pvalue (lag=1) Dip test pvalue
flagevaluation_evp/payloads/scale/2500flags_500users_20fields execution_time [22.105ms; 22.121ms] or [-0.037%; +0.037%] None None None
flagevaluation_evp/payloads/scale/2500flags_500users_20fields throughput [113014.247op/s; 113098.144op/s] or [-0.037%; +0.037%] None None None
flagevaluation_evp/payloads/stress/10flags_1000users_250fields execution_time [103.636ms; 103.705ms] or [-0.033%; +0.033%] None None None
flagevaluation_evp/payloads/stress/10flags_1000users_250fields throughput [9642.849op/s; 9649.137op/s] or [-0.033%; +0.033%] None None None
flagevaluation_evp/payloads/typical/100flags_50users_10fields execution_time [600.029µs; 600.214µs] or [-0.015%; +0.015%] None None None
flagevaluation_evp/payloads/typical/100flags_50users_10fields throughput [166607.558op/s; 166658.638op/s] or [-0.015%; +0.015%] None None None

@dd-octo-sts

dd-octo-sts Bot commented Aug 20, 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.a 89.52 MB 89.52 MB 0% (0 B) 👌
/aarch64-alpine-linux-musl/lib/libdatadog_profiling.so 8.26 MB 8.26 MB 0% (0 B) 👌
aarch64-unknown-linux-gnu
Artifact Baseline Commit Change
/aarch64-unknown-linux-gnu/lib/libdatadog_profiling.a 100.70 MB 100.70 MB 0% (0 B) 👌
/aarch64-unknown-linux-gnu/lib/libdatadog_profiling.so 11.06 MB 11.06 MB 0% (0 B) 👌
libdatadog-x64-windows
Artifact Baseline Commit Change
/libdatadog-x64-windows/debug/dynamic/datadog_profiling_ffi.dll 26.64 MB 26.64 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 180.73 MB 180.75 MB +0% (+16.00 KB) 👌
/libdatadog-x64-windows/debug/static/datadog_profiling_ffi.lib 772.85 MB 772.85 MB 0% (0 B) 👌
/libdatadog-x64-windows/release/dynamic/datadog_profiling_ffi.dll 8.73 MB 8.73 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.65 MB 25.65 MB 0% (0 B) 👌
/libdatadog-x64-windows/release/static/datadog_profiling_ffi.lib 51.09 MB 51.09 MB 0% (0 B) 👌
libdatadog-x86-windows
Artifact Baseline Commit Change
/libdatadog-x86-windows/debug/dynamic/datadog_profiling_ffi.dll 23.22 MB 23.22 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 185.66 MB 185.67 MB +0% (+8.00 KB) 👌
/libdatadog-x86-windows/debug/static/datadog_profiling_ffi.lib 759.09 MB 759.09 MB 0% (0 B) 👌
/libdatadog-x86-windows/release/dynamic/datadog_profiling_ffi.dll 6.74 MB 6.74 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.59 MB 27.59 MB 0% (0 B) 👌
/libdatadog-x86-windows/release/static/datadog_profiling_ffi.lib 48.62 MB 48.62 MB 0% (0 B) 👌
x86_64-alpine-linux-musl
Artifact Baseline Commit Change
/x86_64-alpine-linux-musl/lib/libdatadog_profiling.a 79.78 MB 79.78 MB 0% (0 B) 👌
/x86_64-alpine-linux-musl/lib/libdatadog_profiling.so 9.16 MB 9.16 MB 0% (0 B) 👌
x86_64-unknown-linux-gnu
Artifact Baseline Commit Change
/x86_64-unknown-linux-gnu/lib/libdatadog_profiling.a 95.42 MB 95.42 MB 0% (0 B) 👌
/x86_64-unknown-linux-gnu/lib/libdatadog_profiling.so 11.17 MB 11.17 MB 0% (0 B) 👌

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

Labels

dependencies Pull requests that update a dependency file submodules Pull requests that update submodules code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants