Repository navigation
deps(cargo): bump the rust-minor group across 1 directory with 21 updates - #244
dependabot[bot] wants to merge 1 commit into
Conversation
…ates Bumps the rust-minor group with 21 updates in the / directory: | Package | From | To | | --- | --- | --- | | [serde_json](https://github.com/serde-rs/json) | `1.0.151` | `1.0.154` | | [uuid](https://github.com/uuid-rs/uuid) | `1.26.1` | `1.29.2` | | [tokio](https://github.com/tokio-rs/tokio) | `1.53.1` | `1.54.1` | | [memmap2](https://github.com/RazrFalcon/memmap2-rs) | `0.9.11` | `0.9.12` | | [log](https://github.com/rust-lang/log) | `0.4.34` | `0.4.35` | | [libc](https://github.com/rust-lang/libc) | `0.2.189` | `0.2.191` | | [lazy_static](https://github.com/rust-lang-nursery/lazy-static.rs) | `1.5.0` | `1.5.1` | | [zstd](https://github.com/gyscos/zstd-rs) | `0.14.0` | `0.14.4` | | [trybuild](https://github.com/dtolnay/trybuild) | `1.0.121` | `1.0.122` | | [loom](https://github.com/tokio-rs/loom) | `0.7.2` | `0.7.3` | | [proptest](https://github.com/proptest-rs/proptest) | `1.11.0` | `1.12.0` | | [syn](https://github.com/dtolnay/syn) | `3.0.6` | `3.0.10` | | [cxx](https://github.com/dtolnay/cxx) | `1.0.202` | `1.0.205` | | [cxx-build](https://github.com/dtolnay/cxx) | `1.0.202` | `1.0.205` | | [sha2](https://github.com/RustCrypto/hashes) | `0.11.0` | `0.11.1` | | [flate2](https://github.com/rust-lang/flate2-rs) | `1.1.10` | `1.1.11` | | [open](https://github.com/Byron/open-rs) | `5.4.4` | `5.4.5` | | [tree-sitter](https://github.com/tree-sitter/tree-sitter) | `0.27.0` | `0.27.2` | | [notify](https://github.com/notify-rs/notify) | `8.2.0` | `8.2.2` | | [schemars](https://github.com/GREsau/schemars) | `1.2.2` | `1.2.3` | | [insta](https://github.com/mitsuhiko/insta) | `1.48.0` | `1.49.0` | Updates `serde_json` from 1.0.151 to 1.0.154 - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](serde-rs/json@v1.0.151...v1.0.154) Updates `uuid` from 1.26.1 to 1.29.2 - [Release notes](https://github.com/uuid-rs/uuid/releases) - [Commits](uuid-rs/uuid@v1.26.1...v1.29.2) Updates `tokio` from 1.53.1 to 1.54.1 - [Release notes](https://github.com/tokio-rs/tokio/releases) - [Commits](tokio-rs/tokio@tokio-1.53.1...tokio-1.54.1) Updates `memmap2` from 0.9.11 to 0.9.12 - [Changelog](https://github.com/RazrFalcon/memmap2-rs/blob/master/CHANGELOG.md) - [Commits](RazrFalcon/memmap2-rs@v0.9.11...v0.9.12) Updates `log` from 0.4.34 to 0.4.35 - [Release notes](https://github.com/rust-lang/log/releases) - [Changelog](https://github.com/rust-lang/log/blob/main/CHANGELOG.md) - [Commits](rust-lang/log@0.4.34...v0.4.35) Updates `libc` from 0.2.189 to 0.2.191 - [Release notes](https://github.com/rust-lang/libc/releases) - [Changelog](https://github.com/rust-lang/libc/blob/0.2.191/CHANGELOG.md) - [Commits](rust-lang/libc@0.2.189...0.2.191) Updates `lazy_static` from 1.5.0 to 1.5.1 - [Release notes](https://github.com/rust-lang-nursery/lazy-static.rs/releases) - [Commits](https://github.com/rust-lang-nursery/lazy-static.rs/commits) Updates `zstd` from 0.14.0 to 0.14.4 - [Release notes](https://github.com/gyscos/zstd-rs/releases) - [Commits](gyscos/zstd-rs@v0.14.0...v0.14.4) Updates `trybuild` from 1.0.121 to 1.0.122 - [Release notes](https://github.com/dtolnay/trybuild/releases) - [Commits](dtolnay/trybuild@1.0.121...1.0.122) Updates `loom` from 0.7.2 to 0.7.3 - [Release notes](https://github.com/tokio-rs/loom/releases) - [Changelog](https://github.com/tokio-rs/loom/blob/master/CHANGELOG.md) - [Commits](tokio-rs/loom@v0.7.2...v0.7.3) Updates `proptest` from 1.11.0 to 1.12.0 - [Release notes](https://github.com/proptest-rs/proptest/releases) - [Changelog](https://github.com/proptest-rs/proptest/blob/main/CHANGELOG.md) - [Commits](proptest-rs/proptest@v1.11.0...v1.12.0) Updates `syn` from 3.0.6 to 3.0.10 - [Release notes](https://github.com/dtolnay/syn/releases) - [Commits](dtolnay/syn@3.0.6...3.0.10) Updates `cxx` from 1.0.202 to 1.0.205 - [Release notes](https://github.com/dtolnay/cxx/releases) - [Commits](dtolnay/cxx@1.0.202...1.0.205) Updates `cxx-build` from 1.0.202 to 1.0.205 - [Release notes](https://github.com/dtolnay/cxx/releases) - [Commits](dtolnay/cxx@1.0.202...1.0.205) Updates `sha2` from 0.11.0 to 0.11.1 - [Commits](RustCrypto/hashes@sha2-v0.11.0...sha2-v0.11.1) Updates `flate2` from 1.1.10 to 1.1.11 - [Release notes](https://github.com/rust-lang/flate2-rs/releases) - [Changelog](https://github.com/rust-lang/flate2-rs/blob/main/CHANGELOG.md) - [Commits](rust-lang/flate2-rs@1.1.10...v1.1.11) Updates `open` from 5.4.4 to 5.4.5 - [Release notes](https://github.com/Byron/open-rs/releases) - [Changelog](https://github.com/Byron/open-rs/blob/main/changelog.md) - [Commits](Byron/open-rs@v5.4.4...v5.4.5) Updates `tree-sitter` from 0.27.0 to 0.27.2 - [Release notes](https://github.com/tree-sitter/tree-sitter/releases) - [Commits](tree-sitter/tree-sitter@v0.27.0...v0.27.2) Updates `notify` from 8.2.0 to 8.2.2 - [Release notes](https://github.com/notify-rs/notify/releases) - [Changelog](https://github.com/notify-rs/notify/blob/notify-8.2.2/CHANGELOG.md) - [Commits](notify-rs/notify@notify-8.2.0...notify-8.2.2) Updates `schemars` from 1.2.2 to 1.2.3 - [Release notes](https://github.com/GREsau/schemars/releases) - [Changelog](https://github.com/GREsau/schemars/blob/master/CHANGELOG.md) - [Commits](GREsau/schemars@v1.2.2...v1.2.3) Updates `insta` from 1.48.0 to 1.49.0 - [Release notes](https://github.com/mitsuhiko/insta/releases) - [Changelog](https://github.com/mitsuhiko/insta/blob/master/CHANGELOG.md) - [Commits](mitsuhiko/insta@1.48.0...1.49.0) --- updated-dependencies: - dependency-name: serde_json dependency-version: 1.0.154 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: rust-minor - dependency-name: uuid dependency-version: 1.29.2 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: rust-minor - dependency-name: tokio dependency-version: 1.54.1 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: rust-minor - dependency-name: memmap2 dependency-version: 0.9.12 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: rust-minor - dependency-name: log dependency-version: 0.4.35 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: rust-minor - dependency-name: libc dependency-version: 0.2.191 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: rust-minor - dependency-name: lazy_static dependency-version: 1.5.1 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: rust-minor - dependency-name: zstd dependency-version: 0.14.4 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: rust-minor - dependency-name: trybuild dependency-version: 1.0.122 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: rust-minor - dependency-name: loom dependency-version: 0.7.3 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: rust-minor - dependency-name: proptest dependency-version: 1.12.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: rust-minor - dependency-name: syn dependency-version: 3.0.10 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: rust-minor - dependency-name: cxx dependency-version: 1.0.205 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: rust-minor - dependency-name: cxx-build dependency-version: 1.0.205 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: rust-minor - dependency-name: sha2 dependency-version: 0.11.1 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: rust-minor - dependency-name: flate2 dependency-version: 1.1.11 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: rust-minor - dependency-name: open dependency-version: 5.4.5 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: rust-minor - dependency-name: tree-sitter dependency-version: 0.27.2 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: rust-minor - dependency-name: notify dependency-version: 8.2.2 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: rust-minor - dependency-name: schemars dependency-version: 1.2.3 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: rust-minor - dependency-name: insta dependency-version: 1.49.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: rust-minor ... Signed-off-by: dependabot[bot] <support@github.com>
AssigneesThe following users could not be added as assignees: Please fix the above issues or remove invalid values from |
Benchmark gateBaseline: rolling window of 12 run(s) on Result: FAIL
|
| metric | baseline | current | change | band (<=) | verdict |
|---|---|---|---|---|---|
median |
40.0 ns | 40.0 ns | +0.0% | 65.0 ns | INCONCLUSIVE |
p95 |
50.0 ns | 50.0 ns | +0.0% | 100.0 ns | INCONCLUSIVE |
p99 |
69.0 ns | 69.0 ns | +0.0% | 169.0 ns | INCONCLUSIVE |
p99.9 |
80.0 ns | 80.0 ns | +0.0% | 330.0 ns | INCONCLUSIVE |
p99.99 |
— | 100.0 ns | — | — | N/A (samples) |
max |
14.97 µs | 15.98 µs | +6.8% | 29.93 µs | INCONCLUSIVE |
max_jitter |
14.96 µs | 15.97 µs | +6.8% | 29.92 µs | INCONCLUSIVE |
p99/median |
1.73x | 1.73x | +0.0% | 2.23x | INCONCLUSIVE |
p99.9/median |
2.00x | 2.00x | +0.0% | 3.00x | INCONCLUSIVE |
ns/msg |
169.4 ns | 172.5 ns | +1.9% | 219.4 ns | INCONCLUSIVE |
Adaptive_Imu@304B — 50000 samples
| metric | baseline | current | change | band (<=) | verdict |
|---|---|---|---|---|---|
median |
40.0 ns | 40.0 ns | +0.0% | 65.0 ns | INCONCLUSIVE |
p95 |
60.0 ns | 60.0 ns | +0.0% | 110.0 ns | INCONCLUSIVE |
p99 |
89.0 ns | 89.0 ns | +0.0% | 189.0 ns | INCONCLUSIVE |
p99.9 |
110.0 ns | 110.0 ns | +0.0% | 360.0 ns | INCONCLUSIVE |
p99.99 |
— | 150.0 ns | — | — | N/A (samples) |
max |
12.82 µs | 14.60 µs | +13.9% | 25.64 µs | INCONCLUSIVE |
max_jitter |
12.80 µs | 14.58 µs | +13.9% | 25.60 µs | INCONCLUSIVE |
p99/median |
2.23x | 2.23x | +0.0% | 2.78x | INCONCLUSIVE |
p99.9/median |
2.75x | 2.75x | +0.0% | 3.75x | INCONCLUSIVE |
ns/msg |
268.1 ns | 277.0 ns | +3.3% | 321.8 ns | INCONCLUSIVE |
Adaptive_JointCommand@928B — 50000 samples
| metric | baseline | current | change | band (<=) | verdict |
|---|---|---|---|---|---|
median |
80.0 ns | 70.0 ns | -12.5% | 105.0 ns | IMPROVED |
p95 |
100.0 ns | 100.0 ns | +0.0% | 150.0 ns | INCONCLUSIVE |
p99 |
130.0 ns | 130.0 ns | +0.0% | 230.0 ns | INCONCLUSIVE |
p99.9 |
160.0 ns | 160.0 ns | +0.0% | 410.0 ns | INCONCLUSIVE |
p99.99 |
— | 11.62 µs | — | — | N/A (samples) |
max |
15.33 µs | 15.16 µs | -1.1% | 30.66 µs | INCONCLUSIVE |
max_jitter |
15.28 µs | 15.11 µs | -1.1% | 30.56 µs | INCONCLUSIVE |
p99/median |
1.62x | 1.71x | +5.5% | 2.12x | INCONCLUSIVE |
p99.9/median |
2.00x | 2.14x | +7.1% | 3.00x | INCONCLUSIVE |
ns/msg |
333.7 ns | 337.6 ns | +1.2% | 400.4 ns | INCONCLUSIVE |
Adaptive_LaserScan@1480B — 10000 samples
| metric | baseline | current | change | band (<=) | verdict |
|---|---|---|---|---|---|
median |
89.0 ns | 80.0 ns | -10.1% | 114.0 ns | IMPROVED |
p95 |
110.0 ns | 110.0 ns | +0.0% | 160.0 ns | INCONCLUSIVE |
p99 |
150.0 ns | 150.0 ns | +0.0% | 250.0 ns | INCONCLUSIVE |
p99.9 |
170.0 ns | 170.0 ns | +0.0% | 420.0 ns | INCONCLUSIVE |
p99.99 |
— | 210.0 ns | — | — | N/A (samples) |
max |
12.18 µs | 220.0 ns | -98.2% | 24.36 µs | INCONCLUSIVE |
max_jitter |
12.12 µs | 160.0 ns | -98.7% | 24.24 µs | INCONCLUSIVE |
p99/median |
1.69x | 1.75x | +3.8% | 2.19x | INCONCLUSIVE |
p99.9/median |
1.91x | 2.00x | +4.7% | 2.91x | INCONCLUSIVE |
ns/msg |
688.3 ns | 697.7 ns | +1.4% | 826.0 ns | INCONCLUSIVE |
Topic_cross_process_oneway_paced_stream@1024B — 200000 samples
| metric | baseline | current | change | band (<=) | verdict |
|---|---|---|---|---|---|
median |
260.0 ns | 249.0 ns | -4.2% | 295.6 ns | INCONCLUSIVE |
p95 |
350.0 ns | 340.0 ns | -2.9% | 456.7 ns | INCONCLUSIVE |
p99 |
600.5 ns | 691.0 ns | +15.1% | 1.18 µs | INCONCLUSIVE |
p99.9 |
4.55 µs | 7.51 µs | +64.9% | 16.55 µs | INCONCLUSIVE |
p99.99 |
15.34 µs | 15.93 µs | +3.9% | 24.11 µs | INCONCLUSIVE |
max |
36.45 µs | 48.13 µs | +32.0% | 90.53 µs | INCONCLUSIVE |
max_jitter |
36.24 µs | 47.94 µs | +32.3% | 90.21 µs | INCONCLUSIVE |
p99/median |
2.32x | 2.77x | +19.4% | 4.72x | INCONCLUSIVE |
p99.9/median |
17.72x | 30.05x | +69.6% | 72.08x | INCONCLUSIVE |
ns/msg |
10.00 µs | 10.00 µs | +0.0% | 12.00 µs | INCONCLUSIVE |
Topic_cross_process_oneway_paced_stream@64B — 200000 samples
| metric | baseline | current | change | band (<=) | verdict |
|---|---|---|---|---|---|
median |
170.0 ns | 159.0 ns | -6.5% | 202.6 ns | INCONCLUSIVE |
p95 |
203.0 ns | 200.0 ns | -1.5% | 253.0 ns | INCONCLUSIVE |
p99 |
428.5 ns | 540.0 ns | +26.0% | 739.8 ns | INCONCLUSIVE |
p99.9 |
3.06 µs | 7.10 µs | +132.3% | 9.71 µs | INCONCLUSIVE |
p99.99 |
13.67 µs | 15.65 µs | +14.5% | 27.27 µs | INCONCLUSIVE |
max |
41.88 µs | 32.59 µs | -22.2% | 193.52 µs | INCONCLUSIVE |
max_jitter |
41.77 µs | 32.48 µs | -22.2% | 193.36 µs | INCONCLUSIVE |
p99/median |
2.41x | 3.40x | +41.1% | 3.91x | INCONCLUSIVE |
p99.9/median |
17.95x | 44.67x | +148.9% | 50.82x | INCONCLUSIVE |
ns/msg |
10.00 µs | 10.00 µs | +0.0% | 12.00 µs | INCONCLUSIVE |
Topic_cross_process_oneway_pingpong@1024B — 1000000 samples
| metric | baseline | current | change | band (<=) | verdict |
|---|---|---|---|---|---|
median |
280.5 ns | 281.0 ns | +0.2% | 325.0 ns | INCONCLUSIVE |
p95 |
361.0 ns | 361.0 ns | +0.0% | 415.1 ns | INCONCLUSIVE |
p99 |
406.0 ns | 406.0 ns | +0.0% | 506.0 ns | INCONCLUSIVE |
p99.9 |
1.34 µs | 1.54 µs | +14.9% | 1.90 µs | INCONCLUSIVE |
p99.99 |
10.35 µs | 10.81 µs | +4.5% | 15.53 µs | INCONCLUSIVE |
max |
28.57 µs | 30.07 µs | +5.3% | 114.83 µs | INCONCLUSIVE |
max_jitter |
28.37 µs | 29.88 µs | +5.3% | 114.57 µs | INCONCLUSIVE |
p99/median |
1.45x | 1.43x | -1.0% | 1.95x | INCONCLUSIVE |
p99.9/median |
4.74x | 5.37x | +13.2% | 6.81x | INCONCLUSIVE |
ns/msg |
344.5 ns | 345.3 ns | +0.2% | 413.4 ns | INCONCLUSIVE |
Topic_cross_process_oneway_pingpong@64B — 1000000 samples
| metric | baseline | current | change | band (<=) | verdict |
|---|---|---|---|---|---|
median |
145.0 ns | 150.0 ns | +3.4% | 174.7 ns | INCONCLUSIVE |
p95 |
175.0 ns | 180.0 ns | +2.9% | 225.0 ns | INCONCLUSIVE |
p99 |
195.0 ns | 205.0 ns | +5.1% | 295.0 ns | INCONCLUSIVE |
p99.9 |
718.5 ns | 831.0 ns | +15.7% | 968.5 ns | INCONCLUSIVE |
p99.99 |
7.60 µs | 8.22 µs | +8.2% | 11.40 µs | INCONCLUSIVE |
max |
21.30 µs | 47.49 µs | +123.0% | 54.61 µs | INCONCLUSIVE |
max_jitter |
21.19 µs | 47.37 µs | +123.5% | 54.50 µs | INCONCLUSIVE |
p99/median |
1.34x | 1.33x | -0.4% | 1.84x | INCONCLUSIVE |
p99.9/median |
4.87x | 5.54x | +13.8% | 6.59x | INCONCLUSIVE |
ns/msg |
196.8 ns | 201.6 ns | +2.5% | 246.8 ns | INCONCLUSIVE |
Topic_cross_process_unpaced_queue_delay@64B — 200000 samples
| metric | baseline | current | change | band (<=) | verdict |
|---|---|---|---|---|---|
median |
149.0 ns | 139.0 ns | -6.7% | 174.0 ns | INCONCLUSIVE |
p95 |
200.0 ns | 200.0 ns | +0.0% | 253.4 ns | INCONCLUSIVE |
p99 |
230.5 ns | 290.0 ns | +25.8% | 330.5 ns | INCONCLUSIVE |
p99.9 |
1.97 µs | 9.54 µs | +384.4% | 6.38 µs | REGRESSED |
p99.99 |
8.82 µs | 13.66 µs | +54.8% | 13.24 µs | REGRESSED |
max |
36.69 µs | 44.80 µs | +22.1% | 85.30 µs | INCONCLUSIVE |
max_jitter |
36.59 µs | 44.71 µs | +22.2% | 85.21 µs | INCONCLUSIVE |
p99/median |
1.56x | 2.09x | +33.6% | 2.06x | REGRESSED (blocking) |
p99.9/median |
13.08x | 66.85x | +411.1% | 40.90x | REGRESSED |
ns/msg |
112.0 ns | 115.2 ns | +2.9% | 162.0 ns | INCONCLUSIVE |
Blocking metrics: median, p99/median. Report-only: p95, p99, p99.9, p99.99, max, max_jitter, p99.9/median, ns/msg. Tail metrics past p99.9 are advisory on a shared runner — one host preemption owns max.
Raw benchmark output
ent) 1000000 99.4 139.4 219.6 470.2 9927.2 248965.3 | 999 100
responder turnaround 1000000 29.9 40.1 40.1 40.1 170.1 20597.8 | 650 95
------------------------------------------------------------------------------------------------------------------------------------------
samples=1000000 warmup=200000 transferred=2000000 lost=0 invalid(TSC-skew)=0 poll cost=12.7 ns window=0.408 s
measured window: minor_faults=0 major_faults=0 ctx_switches vol=81 invol=1
core freq cpu3 (measured window only): start=n/a end=n/a min=0MHz max=0MHz mean=0MHz spread=0.00% (n=0)
core freq cpu1 (measured window only): start=n/a end=n/a min=0MHz max=0MHz mean=0MHz spread=0.00% (n=0)
cross-core TSC offset theta_hat = +10.8 ns (clock B - clock A). The `one-way, offset-free` row does not depend on it.
== cross-process ping-pong -- ONE-WAY LATENCY (2 processes, 2 topics, 1 role per handle) ==
json metric key: `Topic_cross_process_oneway_pingpong` (identity used by the CI gate: `Topic_cross_process_oneway_pingpong@1024B`)
payload Probe1k = 1024 B (POD=true) | ring capacity 256 slots | topology 1P/1C | cpu3 <-> cpu1 | pid 7511 <-> pid 7522
------------------------------------------------------------------------------------------------------------------------------------------
metric (ns) n min median p99 p99.9 p99.99 max | n>p99.9 n>p99.99
------------------------------------------------------------------------------------------------------------------------------------------
one-way, offset-free 1000000 195.1 280.5 405.6 1542.8 10639.5 30075.1 | 999 99
round trip (RTT) 1000000 430.6 601.1 841.5 3205.9 21359.1 60190.3 | 999 100
RTT halved (one-way) 1000000 215.3 300.6 420.8 1602.9 10679.6 30095.2 | 999 100
leg A->B (apparent) 1000000 191.0 281.3 451.4 1633.6 20358.1 59800.2 | 996 100
leg B->A (apparent) 1000000 159.5 259.7 430.2 1271.3 11370.2 39070.8 | 1000 100
responder turnaround 1000000 29.9 30.3 40.1 40.1 240.4 23773.8 | 639 98
------------------------------------------------------------------------------------------------------------------------------------------
samples=1000000 warmup=200000 transferred=2000000 lost=0 invalid(TSC-skew)=0 poll cost=34.3 ns window=0.691 s
measured window: minor_faults=0 major_faults=0 ctx_switches vol=136 invol=3
core freq cpu3 (measured window only): start=n/a end=n/a min=0MHz max=0MHz mean=0MHz spread=0.00% (n=0)
core freq cpu1 (measured window only): start=n/a end=n/a min=0MHz max=0MHz mean=0MHz spread=0.00% (n=0)
cross-core TSC offset theta_hat = +10.8 ns (clock B - clock A). The `one-way, offset-free` row does not depend on it.
== cross-process paced stream -- ONE-WAY LATENCY (10000 ns publish period, publisher -> subscriber, direct) ==
json metric key: `Topic_cross_process_oneway_paced_stream` (identity used by the CI gate: `Topic_cross_process_oneway_paced_stream@64B`)
payload Probe64 = 64 B (POD=true) | ring capacity 256 slots | topology 1P/1C | cpu3 <-> cpu1 | pid 7511 <-> pid 7524
------------------------------------------------------------------------------------------------------------------------------------------
metric (ns) n min median p99 p99.9 p99.99 max | n>p99.9 n>p99.99
------------------------------------------------------------------------------------------------------------------------------------------
one-way (assumes TSC coherence) 200000 109.2 159.5 540.2 7102.0 15647.9 32588.7 | 200 20
------------------------------------------------------------------------------------------------------------------------------------------
samples=200000 warmup=20000 transferred=200000 lost=0 invalid(TSC-skew)=0 poll cost=8.6 ns window=2.000 s
measured backlog: 0.02 messages deep on the median sample (ring holds 256); delivered 100.0% of transferred
measured window: minor_faults=0 major_faults=0 ctx_switches vol=394 invol=14
core freq cpu3 (measured window only): start=n/a end=n/a min=0MHz max=0MHz mean=0MHz spread=0.00% (n=0)
core freq cpu1 (measured window only): start=n/a end=n/a min=0MHz max=0MHz mean=0MHz spread=0.00% (n=0)
this row assumes cross-core TSC coherence; theta_hat measured in the ping-pong at this size = +10.8 ns (add to correct).
== cross-process paced stream -- ONE-WAY LATENCY (10000 ns publish period, publisher -> subscriber, direct) ==
json metric key: `Topic_cross_process_oneway_paced_stream` (identity used by the CI gate: `Topic_cross_process_oneway_paced_stream@1024B`)
payload Probe1k = 1024 B (POD=true) | ring capacity 256 slots | topology 1P/1C | cpu3 <-> cpu1 | pid 7511 <-> pid 7526
------------------------------------------------------------------------------------------------------------------------------------------
metric (ns) n min median p99 p99.9 p99.99 max | n>p99.9 n>p99.99
------------------------------------------------------------------------------------------------------------------------------------------
one-way (assumes TSC coherence) 200000 189.3 249.4 690.2 7032.1 15928.4 48127.4 | 199 20
------------------------------------------------------------------------------------------------------------------------------------------
samples=200000 warmup=20000 transferred=200000 lost=0 invalid(TSC-skew)=0 poll cost=20.4 ns window=2.000 s
measured backlog: 0.02 messages deep on the median sample (ring holds 256); delivered 100.0% of transferred
measured window: minor_faults=0 major_faults=0 ctx_switches vol=394 invol=11
core freq cpu3 (measured window only): start=n/a end=n/a min=0MHz max=0MHz mean=0MHz spread=0.00% (n=0)
core freq cpu1 (measured window only): start=n/a end=n/a min=0MHz max=0MHz mean=0MHz spread=0.00% (n=0)
this row assumes cross-core TSC coherence; theta_hat measured in the ping-pong at this size = +10.8 ns (add to correct).
== cross-process unpaced stream -- QUEUE DELAY / BACKPRESSURE, NOT LATENCY (publisher unthrottled; each sample includes its wait in the ring) ==
!! Every number in this block is a PUBLISH-TO-RECEIVE DELAY that INCLUDES
!! time spent waiting in the ring. It is a backpressure/throughput figure.
!! Do not quote it as an IPC latency; that is the exact mistake the retired
!! `Topic_cross_process` metric shipped for months. Read `measured backlog`
!! below: ~1 message means the subscriber kept up and no queue formed.
json metric key: `Topic_cross_process_unpaced_queue_delay` (identity used by the CI gate: `Topic_cross_process_unpaced_queue_delay@64B`)
payload Probe64 = 64 B (POD=true) | ring capacity 256 slots | topology 1P/1C | cpu3 <-> cpu1 | pid 7511 <-> pid 7529
------------------------------------------------------------------------------------------------------------------------------------------
metric (ns) n min median p99 p99.9 p99.99 max | n>p99.9 n>p99.99
------------------------------------------------------------------------------------------------------------------------------------------
publish->receive incl. queue 200000 99.4 139.4 289.5 9536.7 15898.1 42026.4 | 200 20
------------------------------------------------------------------------------------------------------------------------------------------
samples=200000 warmup=20000 transferred=200000 lost=0 invalid(TSC-skew)=0 poll cost=23.7 ns window=0.023 s
measured backlog: 1.21 messages deep on the median sample (ring holds 256); delivered 100.0% of transferred
measured window: minor_faults=0 major_faults=0 ctx_switches vol=5 invol=0
core freq cpu3 (measured window only): start=n/a end=n/a min=0MHz max=0MHz mean=0MHz spread=0.00% (n=0)
core freq cpu1 (measured window only): start=n/a end=n/a min=0MHz max=0MHz mean=0MHz spread=0.00% (n=0)
this row assumes cross-core TSC coherence; theta_hat measured in the ping-pong at this size = +10.8 ns (add to correct).
SUMMARY — one row per published JSON metric (nanoseconds, wall clock)
------------------------------------------------------------------------------------------------------------------------------------------
json metric key what it measures n median p99 p99.9 p99.99 max
------------------------------------------------------------------------------------------------------------------------------------------
Topic_cross_process_oneway_pingpong@64B ONE-WAY latency 1000000 155.0 205.3 871.4 8224.9 124553.2
Topic_cross_process_oneway_pingpong@1024B ONE-WAY latency 1000000 280.5 405.6 1542.8 10639.5 30075.1
Topic_cross_process_oneway_paced_stream@64B ONE-WAY latency 200000 159.5 540.2 7102.0 15647.9 32588.7
Topic_cross_process_oneway_paced_stream@1024B ONE-WAY latency 200000 249.4 690.2 7032.1 15928.4 48127.4
Topic_cross_process_unpaced_queue_delay@64B QUEUE DELAY (not latency) 200000 139.4 289.5 9536.7 15898.1 42026.4
------------------------------------------------------------------------------------------------------------------------------------------
Instrumentation is INCLUDED in every figure and never subtracted.
`Topic_cross_process_oneway_pingpong` is the true one-way figure: it assumes
nothing about cross-core TSC synchronisation and excludes the responder's turnaround.
`RTT halved (one-way)` in the per-scenario tables is a ROUND TRIP DIVIDED BY TWO; it is
the row to compare against any competitor publishing a halved ping-pong.
`Topic_cross_process_unpaced_queue_delay` is a BACKPRESSURE figure: it includes
however long the message waited in the ring, so it scales with the achieved backlog
(printed in its scenario block) and is NOT a latency.
A figure without its payload size, ring depth and topology is not comparable to anything.
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!! THE SAME WARNINGS AGAIN — they apply to every number above
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!! CPU governor is ?/?, not `performance`. RDTSC is a wall clock while the work costs a fixed number of CORE cycles, so every nanosecond below scales with a frequency the governor is free to change. iceoryx2's maintainers measured ~300 ns of difference from the governor alone.
!! No isolcpus= on the kernel command line: the benchmark cores are shared with everything else on this box. The involuntary context-switch count in each scenario block is the mechanism behind the far tail.
!! pingpong (1024 B) `one-way, offset-free`: p99.99 rests on 99 observations. Below ~100 exceedances it is a max wearing a percentile's name; +/-5% needs ~400 (--iterations 4000000).
!! paced_stream (64 B) `one-way (assumes TSC coherence)`: p99.99 rests on 20 observations. Below ~100 exceedances it is a max wearing a percentile's name; +/-5% needs ~400 (--iterations 4000000).
!! paced_stream (1024 B) `one-way (assumes TSC coherence)`: p99.99 rests on 20 observations. Below ~100 exceedances it is a max wearing a percentile's name; +/-5% needs ~400 (--iterations 4000000).
!! unpaced_queue (64 B): measured backlog is only 1.21 messages — the subscriber kept up, so the ring never filled and `Topic_cross_process_unpaced_queue_delay` is NOT a backpressure figure on this run. It is a publish-to-receive delay with no queueing in it, and it is still not a latency (see the paced and ping-pong rows for that).
!! unpaced_queue (64 B) `publish->receive incl. queue`: p99.99 rests on 20 observations. Below ~100 exceedances it is a max wearing a percentile's name; +/-5% needs ~400 (--iterations 4000000).
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Gate report written to /home/runner/work/horus/horus/benchmarks/gate-reports/cross_process-2.json
keys: Topic_cross_process_oneway_pingpong@64B, Topic_cross_process_oneway_pingpong@1024B, Topic_cross_process_oneway_paced_stream@64B, Topic_cross_process_oneway_paced_stream@1024B, Topic_cross_process_unpaced_queue_delay@64B
NOTE: `Topic_cross_process` is retired. A baseline window that still holds it
will report it as missing and fail the gate until the window is refreshed —
that is intended, and is why the key was not silently reused.
Raw samples are omitted (pass --raw-in-json, or --raw-dir for a lossless cycle dump).
7 warning(s) apply to these numbers and are NOT in this file; use --detail-json.
╔══════════════════════════════════════════════════════════════════╗
║ HORUS Robotics Message Types Benchmark ║
╠══════════════════════════════════════════════════════════════════╣
║ Testing real-world robotics message latency (REP 2014) ║
╚══════════════════════════════════════════════════════════════════╝
Platform: AMD EPYC 7763 64-Core Processor (4 cores)
Iterations: 50000
Warmup: 5000
╔═════════════════════════════════════════════════════════════════════════════╗
║ Message Type │ Size (bytes) │ Typical Rate │ Use Case ║
╠═════════════════════════════════════════════════════════════════════════════╣
║ CmdVel │ 16 │ 1000+ Hz │ Velocity control commands ║
║ Imu │ 296 │ 500+ Hz │ IMU sensor fusion ║
║ LaserScan │ 1480 │ 10-40 Hz │ 2D lidar navigation ║
║ JointCommand │ 1032 │ 500+ Hz │ Manipulator control ║
╚═════════════════════════════════════════════════════════════════════════════╝
[Topic] Running benchmarks — timing tx.send() enqueue cost only
(cross-thread consumer drains in the background; no sample
waits for delivery, so these are NOT end-to-end latencies)
─────────────────────────────────────────────────
CmdVel 16 bytes │ median: 40ns │ p99: 69ns │ CV: 3.6557
Imu 304 bytes │ median: 40ns │ p99: 89ns │ CV: 1.7892
LaserScan 1480 bytes │ median: 80ns │ p99: 150ns │ CV: 0.1586
JointCommand 928 bytes │ median: 70ns │ p99: 120ns │ CV: 1.7868
╔══════════════════════════════════════════════════════════════════════════════════════════╗
║ SUMMARY BY MESSAGE TYPE — send() ENQUEUE COST, not end-to-end latency ║
╠══════════════════════════════════════════════════════════════════════════════════════════╣
║ Message │ Size │ Median (ns) │ p99 (ns) │ CV │ Misses │ Sustained rate ║
╠══════════════════════════════════════════════════════════════════════════════════════════╣
║ CmdVel │ 16 │ 40 │ 69 │ 3.6557 │ 0 │ 5.79 M msg/s ║
║ Imu │ 304 │ 40 │ 89 │ 1.7892 │ 0 │ 3.61 M msg/s ║
║ LaserScan │ 1480 │ 80 │ 150 │ 0.1586 │ 0 │ 1.43 M msg/s ║
║ JointCommand │ 928 │ 70 │ 120 │ 1.7868 │ 0 │ 2.96 M msg/s ║
╚══════════════════════════════════════════════════════════════════════════════════════════╝
Sustained rate is wall-clock over the measured loop, so it includes the batch
drain-waits. It is a publish rate for this producer/consumer pair, not a bus limit.
╔══════════════════════════════════════════════════════════════════╗
║ REAL-TIME SUITABILITY ANALYSIS ║
╠══════════════════════════════════════════════════════════════════╣
║ These gates grade the p99 of the send() ENQUEUE COST against one ║
║ whole control period. They are not end-to-end control-loop ║
║ guarantees: a real loop also pays the receive side, the node's ║
║ compute, and the scheduler's jitter, none of which is measured ║
║ here. The headroom is printed so a pass by four orders of ║
║ magnitude cannot be read as a tight result. ║
╠══════════════════════════════════════════════════════════════════╣
║ CmdVel (1kHz control): ~ PASS by 14493x — gate not discriminating (p99=69ns vs 1000000ns)
║ CmdVel (10kHz control): ~ PASS by 1449x — gate not discriminating (p99=69ns vs 100000ns)
║ Imu (500Hz fusion) : ~ PASS by 22472x — gate not discriminating (p99=89ns vs 2000000ns)
║ LaserScan (40Hz lidar) : ~ PASS by 166667x — gate not discriminating (p99=150ns vs 25000000ns)
║ JointCmd (500Hz control): ~ PASS by 16667x — gate not discriminating (p99=120ns vs 2000000ns)
╚══════════════════════════════════════════════════════════════════╝
Results written to: /home/runner/work/horus/horus/benchmarks/gate-reports/robotics-2.json
===== repetition 3/3 =====
HORUS cross-process benchmark — ONE-WAY LATENCY (headline) + unpaced queue delay
Two OS processes on two distinct physical cores over the real Topic SHM transport.
Every handle holds exactly one role, so the `role == Both` same-thread fast path that
produces the repo's headline send-cost figure is never taken. Round-trip rows are
labelled where they are a halved round trip. See the module header for the clock
decomposition and for why the `Topic_cross_process` JSON key was retired.
MACHINE — every nanosecond below is conditional on this block
------------------------------------------------------------------------------------------------------------------------------------------
cpu model : AMD EPYC 7763 64-Core Processor (2 physical / 4 logical cores)
kernel : 7.0.0-1017-azure (x86_64)
benchmark cores : cpu3 = process A (pinger / subscriber), cpu1 = process B (responder / publisher) [DistinctPhysical]
governor : cpu3=n/a cpu1=n/a driver=n/a
scaling range : n/a .. n/a (hw max n/a) turbo_disabled=unknown
clocksource : tsc tsc flags: [tsc, rdtscp, constant_tsc, tsc_reliable, nonstop_tsc]
TSC rate (calibrated) : 2445.512 MHz (0.4089 ns/cycle) — a WALL clock; NOT the core clock
clock instrumentation : 49 cycles = 20.0 ns for serialize()+rdtsc()+rdtscp(), INCLUDED in every sample and never subtracted
transparent_hugepage : always [madvise] never
sched_rt_runtime/period: 950000 / 1000000 us perf_event_paranoid=4
isolcpus=(none) nohz_full=(none) smt_active=1 mlockall(MCL_CURRENT)=true
------------------------------------------------------------------------------------------------------------------------------------------
running ping-pong (one-way latency), 64 B payload ...
running ping-pong (one-way latency), 1024 B payload ...
running paced stream (one-way latency), 64 B payload ...
running paced stream (one-way latency), 1024 B payload ...
running unpaced stream (QUEUE DELAY, not latency), 64 B payload ...
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!! READ THIS BEFORE QUOTING ANY NUMBER BELOW
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!! CPU governor is ?/?, not `performance`. RDTSC is a wall clock while the work costs a fixed number of CORE cycles, so every nanosecond below scales with a frequency the governor is free to change. iceoryx2's maintainers measured ~300 ns of difference from the governor alone.
!! No isolcpus= on the kernel command line: the benchmark cores are shared with everything else on this box. The involuntary context-switch count in each scenario block is the mechanism behind the far tail.
!! paced_stream (64 B) `one-way (assumes TSC coherence)`: p99.99 rests on 20 observations. Below ~100 exceedances it is a max wearing a percentile's name; +/-5% needs ~400 (--iterations 4000000).
!! paced_stream (1024 B) `one-way (assumes TSC coherence)`: p99.99 rests on 20 observations. Below ~100 exceedances it is a max wearing a percentile's name; +/-5% needs ~400 (--iterations 4000000).
!! unpaced_queue (64 B): measured backlog is only 1.20 messages — the subscriber kept up, so the ring never filled and `Topic_cross_process_unpaced_queue_delay` is NOT a backpressure figure on this run. It is a publish-to-receive delay with no queueing in it, and it is still not a latency (see the paced and ping-pong rows for that).
!! unpaced_queue (64 B) `publish->receive incl. queue`: p99.99 rests on 20 observations. Below ~100 exceedances it is a max wearing a percentile's name; +/-5% needs ~400 (--iterations 4000000).
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
== cross-process ping-pong -- ONE-WAY LATENCY (2 processes, 2 topics, 1 role per handle) ==
json metric key: `Topic_cross_process_oneway_pingpong` (identity used by the CI gate: `Topic_cross_process_oneway_pingpong@64B`)
payload Probe64 = 64 B (POD=true) | ring capacity 256 slots | topology 1P/1C | cpu3 <-> cpu1 | pid 7551 <-> pid 7559
------------------------------------------------------------------------------------------------------------------------------------------
metric (ns) n min median p99 p99.9 p99.99 max | n>p99.9 n>p99.99
------------------------------------------------------------------------------------------------------------------------------------------
one-way, offset-free 1000000 120.2 150.1 200.4 811.3 8019.6 20121.8 | 990 100
round trip (RTT) 1000000 280.5 340.6 431.0 1673.3 16760.5 40284.0 | 998 100
RTT halved (one-way) 1000000 140.3 170.3 215.5 836.6 8380.2 20142.0 | 998 100
leg A->B (apparent) 1000000 121.0 161.1 221.2 1233.3 10520.1 40064.4 | 988 100
leg B->A (apparent) 1000000 99.4 139.4 209.8 530.0 8815.3 27379.5 | 996 100
responder turnaround 1000000 29.9 40.1 40.1 40.1 170.5 32239.1 | 526 85
------------------------------------------------------------------------------------------------------------------------------------------
samples=1000000 warmup=200000 transferred=2000000 lost=0 invalid(TSC-skew)=0 poll cost=13.9 ns window=0.401 s
measured window: minor_faults=0 major_faults=0 ctx_switches vol=79 invol=3
core freq cpu3 (measured window only): start=n/a end=n/a min=0MHz max=0MHz mean=0MHz spread=0.00% (n=0)
core freq cpu1 (measured window only): start=n/a end=n/a min=0MHz max=0MHz mean=0MHz spread=0.00% (n=0)
cross-core TSC offset theta_hat = +10.8 ns (clock B - clock A). The `one-way, offset-free` row does not depend on it.
== cross-process ping-pong -- ONE-WAY LATENCY (2 processes, 2 topics, 1 role per handle) ==
json metric key: `Topic_cross_process_oneway_pingpong` (identity used by the CI gate: `Topic_cross_process_oneway_pingpong@1024B`)
payload Probe1k = 1024 B (POD=true) | ring capacity 256 slots | topology 1P/1C | cpu3 <-> cpu1 | pid 7551 <-> pid 7561
------------------------------------------------------------------------------------------------------------------------------------------
metric (ns) n min median p99 p99.9 p99.99 max | n>p99.9 n>p99.99
------------------------------------------------------------------------------------------------------------------------------------------
one-way, offset-free 1000000 195.1 280.1 400.7 1472.9 10814.9 33291.2 | 1000 100
round trip (RTT) 1000000 430.6 591.3 831.7 3075.4 21820.0 66612.2 | 1000 100
RTT halved (one-way) 1000000 215.3 295.6 415.9 1537.7 10910.0 33306.1 | 1000 100
leg A->B (apparent) 1000000 191.0 271.5 441.6 1533.8 20367.9 63998.0 | 997 100
leg B->A (apparent) 1000000 159.5 269.9 430.2 1441.8 11400.1 66290.8 | 999 100
responder turnaround 1000000 29.9 30.3 40.1 40.1 260.5 23783.6 | 696 98
------------------------------------------------------------------------------------------------------------------------------------------
samples=1000000 warmup=200000 transferred=2000000 lost=0 invalid(TSC-skew)=0 poll cost=39.7 ns window=0.683 s
measured window: minor_faults=0 major_faults=0 ctx_switches vol=135 invol=3
core freq cpu3 (measured window only): start=n/a end=n/a min=0MHz max=0MHz mean=0MHz spread=0.00% (n=0)
core freq cpu1 (measured window only): start=n/a end=n/a min=0MHz max=0MHz mean=0MHz spread=0.00% (n=0)
cross-core TSC offset theta_hat = +0.8 ns (clock B - clock A). The `one-way, offset-free` row does not depend on it.
== cross-process paced stream -- ONE-WAY LATENCY (10000 ns publish period, publisher -> subscriber, direct) ==
json metric key: `Topic_cross_process_oneway_paced_stream` (identity used by the CI gate: `Topic_cross_process_oneway_paced_stream@64B`)
payload Probe64 = 64 B (POD=true) | ring capacity 256 slots | topology 1P/1C | cpu3 <-> cpu1 | pid 7551 <-> pid 7563
------------------------------------------------------------------------------------------------------------------------------------------
metric (ns) n min median p99 p99.9 p99.99 max | n>p99.9 n>p99.99
------------------------------------------------------------------------------------------------------------------------------------------
one-way (assumes TSC coherence) 200000 109.2 159.5 509.9 3856.5 14385.5 28221.1 | 200 20
------------------------------------------------------------------------------------------------------------------------------------------
samples=200000 warmup=20000 transferred=200000 lost=0 invalid(TSC-skew)=0 poll cost=8.6 ns window=2.000 s
measured backlog: 0.02 messages deep on the median sample (ring holds 256); delivered 100.0% of transferred
measured window: minor_faults=0 major_faults=0 ctx_switches vol=394 invol=9
core freq cpu3 (measured window only): start=n/a end=n/a min=0MHz max=0MHz mean=0MHz spread=0.00% (n=0)
core freq cpu1 (measured window only): start=n/a end=n/a min=0MHz max=0MHz mean=0MHz spread=0.00% (n=0)
this row assumes cross-core TSC coherence; theta_hat measured in the ping-pong at this size = +10.8 ns (add to correct).
== cross-process paced stream -- ONE-WAY LATENCY (10000 ns publish period, publisher -> subscriber, direct) ==
json metric key: `Topic_cross_process_oneway_paced_stream` (identity used by the CI gate: `Topic_cross_process_oneway_paced_stream@1024B`)
payload Probe1k = 1024 B (POD=true) | ring capacity 256 slots | topology 1P/1C | cpu3 <-> cpu1 | pid 7551 <-> pid 7565
------------------------------------------------------------------------------------------------------------------------------------------
metric (ns) n min median p99 p99.9 p99.99 max | n>p99.9 n>p99.99
------------------------------------------------------------------------------------------------------------------------------------------
one-way (assumes TSC coherence) 200000 179.5 249.8 690.7 7512.9 14014.7 26567.9 | 200 20
------------------------------------------------------------------------------------------------------------------------------------------
samples=200000 warmup=20000 transferred=200000 lost=0 invalid(TSC-skew)=0 poll cost=20.9 ns window=2.000 s
measured backlog: 0.02 messages deep on the median sample (ring holds 256); delivered 100.0% of transferred
measured window: minor_faults=0 major_faults=0 ctx_switches vol=394 invol=9
core freq cpu3 (measured window only): start=n/a end=n/a min=0MHz max=0MHz mean=0MHz spread=0.00% (n=0)
core freq cpu1 (measured window only): start=n/a end=n/a min=0MHz max=0MHz mean=0MHz spread=0.00% (n=0)
this row assumes cross-core TSC coherence; theta_hat measured in the ping-pong at this size = +0.8 ns (add to correct).
== cross-process unpaced stream -- QUEUE DELAY / BACKPRESSURE, NOT LATENCY (publisher unthrottled; each sample includes its wait in the ring) ==
!! Every number in this block is a PUBLISH-TO-RECEIVE DELAY that INCLUDES
!! time spent waiting in the ring. It is a backpressure/throughput figure.
!! Do not quote it as an IPC latency; that is the exact mistake the retired
!! `Topic_cross_process` metric shipped for months. Read `measured backlog`
!! below: ~1 message means the subscriber kept up and no queue formed.
json metric key: `Topic_cross_process_unpaced_queue_delay` (identity used by the CI gate: `Topic_cross_process_unpaced_queue_delay@64B`)
payload Probe64 = 64 B (POD=true) | ring capacity 256 slots | topology 1P/1C | cpu3 <-> cpu1 | pid 7551 <-> pid 7568
------------------------------------------------------------------------------------------------------------------------------------------
metric (ns) n min median p99 p99.9 p99.99 max | n>p99.9 n>p99.99
------------------------------------------------------------------------------------------------------------------------------------------
publish->receive incl. queue 200000 89.1 139.4 239.6 2263.3 12993.2 44801.3 | 200 20
------------------------------------------------------------------------------------------------------------------------------------------
samples=200000 warmup=20000 transferred=200000 lost=0 invalid(TSC-skew)=0 poll cost=19.2 ns window=0.023 s
measured backlog: 1.20 messages deep on the median sample (ring holds 256); delivered 100.0% of transferred
measured window: minor_faults=0 major_faults=0 ctx_switches vol=5 invol=0
core freq cpu3 (measured window only): start=n/a end=n/a min=0MHz max=0MHz mean=0MHz spread=0.00% (n=0)
core freq cpu1 (measured window only): start=n/a end=n/a min=0MHz max=0MHz mean=0MHz spread=0.00% (n=0)
this row assumes cross-core TSC coherence; theta_hat measured in the ping-pong at this size = +10.8 ns (add to correct).
SUMMARY — one row per published JSON metric (nanoseconds, wall clock)
------------------------------------------------------------------------------------------------------------------------------------------
json metric key what it measures n median p99 p99.9 p99.99 max
------------------------------------------------------------------------------------------------------------------------------------------
Topic_cross_process_oneway_pingpong@64B ONE-WAY latency 1000000 150.1 200.4 811.3 8019.6 20121.8
Topic_cross_process_oneway_pingpong@1024B ONE-WAY latency 1000000 280.1 400.7 1472.9 10814.9 33291.2
Topic_cross_process_oneway_paced_stream@64B ONE-WAY latency 200000 159.5 509.9 3856.5 14385.5 28221.1
Topic_cross_process_oneway_paced_stream@1024B ONE-WAY latency 200000 249.8 690.7 7512.9 14014.7 26567.9
Topic_cross_process_unpaced_queue_delay@64B QUEUE DELAY (not latency) 200000 139.4 239.6 2263.3 12993.2 44801.3
------------------------------------------------------------------------------------------------------------------------------------------
Instrumentation is INCLUDED in every figure and never subtracted.
`Topic_cross_process_oneway_pingpong` is the true one-way figure: it assumes
nothing about cross-core TSC synchronisation and excludes the responder's turnaround.
`RTT halved (one-way)` in the per-scenario tables is a ROUND TRIP DIVIDED BY TWO; it is
the row to compare against any competitor publishing a halved ping-pong.
`Topic_cross_process_unpaced_queue_delay` is a BACKPRESSURE figure: it includes
however long the message waited in the ring, so it scales with the achieved backlog
(printed in its scenario block) and is NOT a latency.
A figure without its payload size, ring depth and topology is not comparable to anything.
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!! THE SAME WARNINGS AGAIN — they apply to every number above
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!! CPU governor is ?/?, not `performance`. RDTSC is a wall clock while the work costs a fixed number of CORE cycles, so every nanosecond below scales with a frequency the governor is free to change. iceoryx2's maintainers measured ~300 ns of difference from the governor alone.
!! No isolcpus= on the kernel command line: the benchmark cores are shared with everything else on this box. The involuntary context-switch count in each scenario block is the mechanism behind the far tail.
!! paced_stream (64 B) `one-way (assumes TSC coherence)`: p99.99 rests on 20 observations. Below ~100 exceedances it is a max wearing a percentile's name; +/-5% needs ~400 (--iterations 4000000).
!! paced_stream (1024 B) `one-way (assumes TSC coherence)`: p99.99 rests on 20 observations. Below ~100 exceedances it is a max wearing a percentile's name; +/-5% needs ~400 (--iterations 4000000).
!! unpaced_queue (64 B): measured backlog is only 1.20 messages — the subscriber kept up, so the ring never filled and `Topic_cross_process_unpaced_queue_delay` is NOT a backpressure figure on this run. It is a publish-to-receive delay with no queueing in it, and it is still not a latency (see the paced and ping-pong rows for that).
!! unpaced_queue (64 B) `publish->receive incl. queue`: p99.99 rests on 20 observations. Below ~100 exceedances it is a max wearing a percentile's name; +/-5% needs ~400 (--iterations 4000000).
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Gate report written to /home/runner/work/horus/horus/benchmarks/gate-reports/cross_process-3.json
keys: Topic_cross_process_oneway_pingpong@64B, Topic_cross_process_oneway_pingpong@1024B, Topic_cross_process_oneway_paced_stream@64B, Topic_cross_process_oneway_paced_stream@1024B, Topic_cross_process_unpaced_queue_delay@64B
NOTE: `Topic_cross_process` is retired. A baseline window that still holds it
will report it as missing and fail the gate until the window is refreshed —
that is intended, and is why the key was not silently reused.
Raw samples are omitted (pass --raw-in-json, or --raw-dir for a lossless cycle dump).
6 warning(s) apply to these numbers and are NOT in this file; use --detail-json.
╔══════════════════════════════════════════════════════════════════╗
║ HORUS Robotics Message Types Benchmark ║
╠══════════════════════════════════════════════════════════════════╣
║ Testing real-world robotics message latency (REP 2014) ║
╚══════════════════════════════════════════════════════════════════╝
Platform: AMD EPYC 7763 64-Core Processor (4 cores)
Iterations: 50000
Warmup: 5000
╔═════════════════════════════════════════════════════════════════════════════╗
║ Message Type │ Size (bytes) │ Typical Rate │ Use Case ║
╠═════════════════════════════════════════════════════════════════════════════╣
║ CmdVel │ 16 │ 1000+ Hz │ Velocity control commands ║
║ Imu │ 296 │ 500+ Hz │ IMU sensor fusion ║
║ LaserScan │ 1480 │ 10-40 Hz │ 2D lidar navigation ║
║ JointCommand │ 1032 │ 500+ Hz │ Manipulator control ║
╚═════════════════════════════════════════════════════════════════════════════╝
[Topic] Running benchmarks — timing tx.send() enqueue cost only
(cross-thread consumer drains in the background; no sample
waits for delivery, so these are NOT end-to-end latencies)
─────────────────────────────────────────────────
CmdVel 16 bytes │ median: 40ns │ p99: 69ns │ CV: 2.3132
Imu 304 bytes │ median: 40ns │ p99: 89ns │ CV: 2.5915
LaserScan 1480 bytes │ median: 80ns │ p99: 140ns │ CV: 0.1555
JointCommand 928 bytes │ median: 70ns │ p99: 130ns │ CV: 1.9796
╔══════════════════════════════════════════════════════════════════════════════════════════╗
║ SUMMARY BY MESSAGE TYPE — send() ENQUEUE COST, not end-to-end latency ║
╠══════════════════════════════════════════════════════════════════════════════════════════╣
║ Message │ Size │ Median (ns) │ p99 (ns) │ CV │ Misses │ Sustained rate ║
╠══════════════════════════════════════════════════════════════════════════════════════════╣
║ CmdVel │ 16 │ 40 │ 69 │ 2.3132 │ 0 │ 5.80 M msg/s ║
║ Imu │ 304 │ 40 │ 89 │ 2.5915 │ 0 │ 3.60 M msg/s ║
║ LaserScan │ 1480 │ 80 │ 140 │ 0.1555 │ 0 │ 1.44 M msg/s ║
║ JointCommand │ 928 │ 70 │ 130 │ 1.9796 │ 0 │ 2.97 M msg/s ║
╚══════════════════════════════════════════════════════════════════════════════════════════╝
Sustained rate is wall-clock over the measured loop, so it includes the batch
drain-waits. It is a publish rate for this producer/consumer pair, not a bus limit.
╔══════════════════════════════════════════════════════════════════╗
║ REAL-TIME SUITABILITY ANALYSIS ║
╠══════════════════════════════════════════════════════════════════╣
║ These gates grade the p99 of the send() ENQUEUE COST against one ║
║ whole control period. They are not end-to-end control-loop ║
║ guarantees: a real loop also pays the receive side, the node's ║
║ compute, and the scheduler's jitter, none of which is measured ║
║ here. The headroom is printed so a pass by four orders of ║
║ magnitude cannot be read as a tight result. ║
╠══════════════════════════════════════════════════════════════════╣
║ CmdVel (1kHz control): ~ PASS by 14493x — gate not discriminating (p99=69ns vs 1000000ns)
║ CmdVel (10kHz control): ~ PASS by 1449x — gate not discriminating (p99=69ns vs 100000ns)
║ Imu (500Hz fusion) : ~ PASS by 22472x — gate not discriminating (p99=89ns vs 2000000ns)
║ LaserScan (40Hz lidar) : ~ PASS by 178571x — gate not discriminating (p99=140ns vs 25000000ns)
║ JointCmd (500Hz control): ~ PASS by 15385x — gate not discriminating (p99=130ns vs 2000000ns)
╚══════════════════════════════════════════════════════════════════╝
Results written to: /home/runner/work/horus/horus/benchmarks/gate-reports/robotics-3.json
Gated against a rolling window of recent main runs. Each metric's band is max(relative, center + k·sigma_observed, absolute floor), so it is derived from the noise the baseline itself measured — where a band is printed wider than the change you care about, this run did not detect a regression and could not have. Thresholds and their reasoning: RegressionPolicy in benchmarks/src/output.rs.
Commit: 865c690
Bumps the rust-minor group with 21 updates in the / directory:
1.0.1511.0.1541.26.11.29.21.53.11.54.10.9.110.9.120.4.340.4.350.2.1890.2.1911.5.01.5.10.14.00.14.41.0.1211.0.1220.7.20.7.31.11.01.12.03.0.63.0.101.0.2021.0.2051.0.2021.0.2050.11.00.11.11.1.101.1.115.4.45.4.50.27.00.27.28.2.08.2.21.2.21.2.31.48.01.49.0Updates
serde_jsonfrom 1.0.151 to 1.0.154Release notes
Sourced from serde_json's releases.
Commits
20572a6Release 1.0.154a91bfafFix RandomState links in map documentation3c932c0Merge pull request #1333 from razmser/no-std-preserve-order4b2d726Release 1.0.15383335eeTouch up PR 13454b4810aResolve range_plus_one pedantic clippy lint8af71ccMerge pull request #1345 from 00200200/fix-invalid-utf8-error-column452afa2Correct multiline raw UTF-8 error positions and simplify indexingc9f1e3bRelease 1.0.152854fc70Touch up PR 1347Updates
uuidfrom 1.26.1 to 1.29.2Release notes
Sourced from uuid's releases.
Commits
5205a6eMerge pull request #929 from uuid-rs/cargo/v1.29.2ff39846prepare for 1.29.2 releasec879f61Merge pull request #928 from nickbabcock/wasm644b57852Support wasm64 in the js feature0fe2dabMerge pull request #927 from uuid-rs/cargo/v1.29.18896d2eprepare for 1.29.1 release2eef370Merge pull request #926 from uuid-rs/fix/timestamp-edgesde33fdefix up several bugs in v7 monotonicity raised by automated scanning7c7326dMerge pull request #923 from uuid-rs/fix/deprecate-borsh13e1ff0deprecate theborshfeature ofuuidin favour of auuidfeature inborshUpdates
tokiofrom 1.53.1 to 1.54.1Release notes
Sourced from tokio's releases.
... (truncated)
Commits
b53b200chore: prepare Tokio v1.54.1 (#8693)5ed619btime: revert "remove the runtime handle from timers" (#8692)66d34e4chore: prepare Tokio v1.54.0 (#8667)0d322ceio: support vectored writes in sink (#8663)4167c56codec: expose I/O sources from codec errors (#8665)cdd9daefs: propagate iouring stress test failures (#8644)52ac781ci: run the emscripten JSPI tests as an auto-initialized ES module (#8640)4890d02stream: implementFusedStreamforJoinSetStream(#8629)a6bd8e1wasm: check Emscripten version when using JSPI (#8627)9dd749dMerge 'tokio-1.53.3' into 'master' (#8641)Updates
memmap2from 0.9.11 to 0.9.12Changelog
Sourced from memmap2's changelog.
Commits
4692b05Merge pull request #180 from RazrFalcon/release/v0.9.129e5c0eeBump version to 0.9.12.b98035dMerge pull request #177 from JaskRendix/extract-test-suite0986677Merge branch 'master' into extract-test-suited26cc84Fix map_if_safe() stub.145ee36Silence clippy warning about trivial identical match arms.b402ef2Fix check_safe_to_map() on Apple targets.b544238Fix formatting.f50e480Move tests to test/ folder.0994bf7Merge pull request #176 from hiyms/feat/support-ohosUpdates
logfrom 0.4.34 to 0.4.35Release notes
Sourced from log's releases.
Changelog
Sourced from log's changelog.
Commits
a46450bUpdate CHANGELOG.mda715f17chore: release v0.4.35b4e2b12Merge pull request #747 from rust-lang/chore/release-plz-mgnt6b490b6run fmt2c7fd52simplify some crate release tasks for easier automation5bc5545Merge pull request #745 from marcoienibot/release-plz-disable-semver-check4234b8cDisable release-plz semver check95918ffMerge pull request #744 from Kobzol/trusted-publishinge7ed747Fix Zizmor lintse87a3c6Setup trusted publishingUpdates
libcfrom 0.2.189 to 0.2.191Release notes
Sourced from libc's releases.
... (truncated)
Changelog
Sourced from libc's changelog.
... (truncated)
Commits
ccc2ff4libc: Release 0.2.191bce6efbapple: Addmach_task_selfandmach_task_self_to semver checksecf4fd4apple: Re-restrictmach_vm_mapto MacOS-onlyb0e0423Revert "apple: Disablemach.hAPI on Apple mobile OSs"9c7f568apple: addifaliasreqandin6_aliasreq018c7e9wasi: Add pthread_condattr_{get,set}clock2c77185openbsd: add sensordev structuree10813churd: Add missingPOSIX_SPAWN_*flags2ea4bc1Fix FreeBSD/aarch646d666fddragonfly: Parse version from headers rather than CLIUpdates
lazy_staticfrom 1.5.0 to 1.5.1Commits
Updates
zstdfrom 0.14.0 to 0.14.4Commits
5c4970bRelease zstd 0.14.4, zstd-safe 8.3.0, and zstd-sys 2.1.33375874zstd-sys: drop the macOS wasm compiler probefa82b4cbench: add revisions.sh, to compare revisions over every groupd017a8abulk: reset the session when compress_to_buffer failse65916czstd-safe: wait for zstdmt jobs before abandoning or freeing a framef67ade3zstd-sys: stop building zstd with -fmerge-all-constantsdf80a67rust-backend: refuse seekable, test it in CI, and document it3bd9535bench: compare backends, with a levels group and a chart02103aczstd-sys: prototype a rust-backend feature using libzstd-rs-sysf8d2249zstd-safe: let init_using_{c,d}dict recover a poisoned contextUpdates
trybuildfrom 1.0.121 to 1.0.122Release notes
Sourced from trybuild's releases.
Commits
3f6a324Release 1.0.122ce13e9bMerge pull request 344 from tamaro-skaljic/fix/issue-343-unused-workspace-dep...d027c0bCopy only inherited workspace dependencies into generated manifestUpdates
loomfrom 0.7.2 to 0.7.3Release notes
Sourced from loom's releases.
Changelog
Sourced from loom's changelog.
Commits
9d549cdPrepare v0.7.3 release (#436)acaa24aExtend the 32-bit fix to the test suite (#434)64da2f6atomic: Addtry_updateandupdate(#429)948c8cctests: Fix typo: mutal -> mutual (#404)6abd413add?Sizedtrait bound toRwLock(#401)dbf32b0Add license badge in README (#381)2dc2327Fix discord link (#380)850facaDocumentNotifylimitation (#373)0624ff3Fix build error on not 64 bit arch (#370)3ef62e2Document what effect hints have on loom (#358)Updates
proptestfrom 1.11.0 to 1.12.0Commits
70cf37dMerge pull request #675 from proptest-rs/prep-1.12729e0ffprepare next releases and fix panic handling28c1fadMerge pull request #664 from Expyron/main5ddd9a4Merge pull request #668 from toddATavail/fix-fork-persisted-failurea6a9ac7Merge pull request #673 from glaziermag/fix-book-deployd57d88bReplacerand_chachawithchacha209411213Deploy the book on pushes to main1719745fix: terminate the fork replay when a persisted failure fails0f55b7atest: a persisted failure in a forked test must be reported4b0594eMerge pull request #669 from proptest-rs/no-fail-fastUpdates
synfrom 3.0.6 to 3.0.10Release notes
Sourced from syn's releases.
Commits
97ec37dRelease 3.0.10d12a53fMerge pull request #2090 from LucaCappelletti94/upstream/fixup-linear-scan75cc9dcUpdate test suite to nightly-2026-11-08cbc91c4Update test suite to nightly-2026-11-0338318bfUpdate test suite to nightly-2026-10-304afbff6Skip rescanning operands whose scan already failedf81c060Update test suite to nightly-2026-10-27acfda91Update test suite to nightly-2026-10-269ff9287Update test suite to nightly-2026-10-157c44a55Release 3.0.9Updates
cxxfrom 1.0.202 to 1.0.205Release notes
Sourced from cxx's releases.
Commits
598ccd9Release 1.0.2050a3abc9Merge pull request #1767 from dtolnay/debugassertions7d13af3Mark debug_assertions special case for future removald45597dUpdate bazel apple_support module version061094aLockfile updatede8799bMerge pull request #1766 from dtolnay/cfgfeature0047be1Remove handling of CARGO_FEATURE_ in favor of 1.85's CARGO_CFG_FEATUREc2413dcRelease 1.0.2048f422a5Lockfile update940cdcaMerge pull request #1765 from dtolnay/dataUpdates
cxx-buildfrom 1.0.202 to 1.0.205Release notes
Sourced from cxx-build's releases.
Commits
598ccd9Release 1.0.2050a3abc9Merge pull request #1767 from dtolnay/debugassertions7d13af3Mark debug_assertions special case for future removald45597dUpdate bazel apple_support module version061094aLockfile updatede8799bMerge pull request #1766 from dtolnay/cfgfeature0047be1Remove handling of CARGO_FEATURE_ in favor of 1.85's CARGO_CFG_FEATUREc2413dcRelease 1.0.2048f422a5Lockfile update940cdcaMerge pull request #1765 from dtolnay/dataUpdates
sha2from 0.11.0 to 0.11.1Commits
138dc5aRelease sha2 v0.11.1 (#927)cf01056sha2: fixunsafe_op_in_unsafe_fnlint, bump MSRV to 1.88 (#926)7c59cadUpdate Cargo.lock (#921)f57b947streebog: tweak internal implementation (#925)336611fFixcargo::manual_readmelint (#924)1df8877md2: fixclippy::needless_range_looplint (#923)6075989sha2: fix loading of round constants on AArch64 backends (#922)eadfd90Update Cargo.lock (#913)fa30840blake2 v0.11.0 (#911)f6c786dci: bump the all-deps group across 1 directory with 3 updates (#896)Updates
flate2from 1.1.10 to 1.1.11Release notes
Sourced from flate2's releases.
Changelog
Sourced from flate2's changelog.