Skip to content

Benchmark results for unilink v0.8.6 on jetson-orin-nano

Choose a tag to compare

@github-actions github-actions released this 04 Jul 07:30
· 10 commits to main since this release

Self-hosted benchmark results for unilink v0.8.6.

Benchmark Target

  • unilink ref: v0.8.6
  • unilink commit: ac6b44c9a7216fc74eb3ea14f2b45e561045ac22
  • reference platform: jetson-orin-nano
  • platform suffix: jetson-orin-nano
  • benchmark repo commit: eb3a4f730d0df20027ae8c344e891df734c55ac7
  • GitHub run id: 28698901133
  • measured at UTC: 2026-07-04T07:22:43Z

Runner Environment

  • runner: ubuntu-arm64
  • host: ubuntu
  • OS: Ubuntu 22.04.5 LTS
  • kernel: 5.15.185-tegra
  • architecture: aarch64
  • CPU: Cortex-A78AE
  • logical CPUs: 6
  • estimated physical cores: 6
  • memory KiB: 7789888
  • compiler: c++ (Ubuntu 11.4.0-1ubuntu1~22.04.3) 11.4.0
  • CMake: cmake version 4.3.4

Jetson Environment

  • Jetson model: NVIDIA Jetson Orin Nano Engineering Reference Developer Kit Super
  • L4T release: `# R36 (release), REVISION: 5.0, GCID: 43688277, BOARD: generic, EABI: aarch64, DATE: Fri Jan 16 03:50:45 UTC 2026

KERNEL_VARIANT: oot

TARGET_USERSPACE_LIB_DIR=nvidia
TARGET_USERSPACE_LIB_DIR_PATH=usr/lib/aarch64-linux-gnu/nvidia`

  • nvpmodel: NV Power Mode: MAXN_SUPER
  • jetson_clocks: SOC family:tegra234 Machine:NVIDIA Jetson Orin Nano Engineering Reference Developer Kit Super

Latency Summary

transport payload runs msg/s median MiB/s median p50 us p95 us p99 us p99.9 us max us >5ms >10ms >50ms
tcp 64 3 7837 0.48 127 137 159 239 787 0 0 0
tcp 256 3 8275 2.02 120 131 153 257 1032 0 0 0
tcp 1024 3 8198 8.01 124 139 167 250 847 0 0 0
tcp 4096 3 5781 22.58 157 250 304 534 944 0 0 0
tcp 16384 3 3464 54.13 282 341 396 626 884 0 0 0
tcp 65536 3 1864 116.49 531 564 604 949 1418 0 0 0
udp 64 3 8685 0.53 114 125 163 260 1023 0 0 0
udp 256 3 9785 2.39 100 108 138 253 689 0 0 0
udp 1024 3 8405 8.21 119 129 190 248 2112 0 0 0
uds 64 3 14328 0.87 69 76 131 183 1446 0 0 0
uds 256 3 14129 3.45 69 85 123 167 497 0 0 0
uds 1024 3 13360 13.05 73 95 141 171 880 0 0 0
uds 4096 3 9030 35.27 112 138 161 236 1088 0 0 0
uds 16384 3 4723 73.80 211 246 265 327 1393 0 0 0
uds 65536 3 3459 216.21 282 298 308 380 713 0 0 0

Strategy Summary

transport strategy payload runs accepted MiB/s received MiB/s delivery % failed sends runtime stats dropped msg dropped MiB max queue KiB bp events
tcp besteffort 64 3 6.31 6.31 100.00 24810 yes 24810 1.51 1024 70
tcp besteffort 256 3 21.73 21.73 100.00 24935 yes 24935 6.09 1024 246
tcp besteffort 1024 3 93.41 93.41 100.00 23068 yes 23068 22.53 1024 978
tcp besteffort 4096 3 280.83 280.83 100.00 25527 yes 25527 99.71 1024 2996
tcp besteffort 16384 3 1070.28 1070.28 100.00 21712 yes 21712 339.25 1024 8650
tcp besteffort 65536 3 1088.58 1088.58 100.00 18172 yes 18172 1135.75 1024 7380
tcp reliable 64 3 5.55 5.55 100.00 0 yes 0 0 1026.12 58
tcp reliable 256 3 18.54 18.54 100.00 0 yes 0 0 1035.50 208
tcp reliable 1024 3 72.14 72.14 100.00 0 yes 0 0 1068 784
tcp reliable 4096 3 271.29 271.29 100.00 0 yes 0 0 1216 3000
tcp reliable 16384 3 1120.59 1120.59 100.00 0 yes 0 0 1872 11524
tcp reliable 65536 3 1106.17 1106.17 100.00 0 yes 0 0 2496 10484
udp besteffort 64 3 8.13 8.13 99.96 21440 yes 21440 1.31 1024 88
udp besteffort 256 3 29.57 29.54 99.89 21611 yes 21611 5.28 1024 324
udp besteffort 1024 3 110.73 110.40 99.72 21123 yes 21123 20.63 1024 1160
udp besteffort 4096 3 375.87 375.87 99.97 21179 yes 21179 82.73 1024 3750
udp besteffort 16384 3 1001.21 999.19 99.89 21649 yes 21649 338.27 1024 9058
udp besteffort 65536 3 0.06 0.00 0.00 26016 yes 0 0 64 0
udp reliable 64 3 6.86 6.86 100.00 0 yes 0 0 1024.50 72
udp reliable 256 3 28.00 28.00 100.00 0 yes 0 0 1028.50 296
udp reliable 1024 3 98.24 98.24 100.00 0 yes 0 0 1037 1022
udp reliable 4096 3 340.00 339.95 99.99 0 yes 0 0 1216 3692
udp reliable 16384 3 1021.24 1020.98 99.98 0 yes 0 0 1440 11220
udp reliable 65536 3 0.08 0.00 0.00 27987 yes 0 0 64 0
uds besteffort 64 3 11.75 11.75 100.00 14593 yes 14593 0.89 1024 110
uds besteffort 256 3 43.03 43.03 100.00 12775 yes 12775 3.12 1024 404
uds besteffort 1024 3 140.18 140.18 100.00 10602 yes 10602 10.35 1024 1196
uds besteffort 4096 3 478.96 478.96 100.00 14728 yes 14728 57.53 1024 4042
uds besteffort 16384 3 1148.73 1148.73 100.00 20782 yes 20782 324.72 1024 9976
uds besteffort 65536 3 1231.75 1231.75 100.00 18423 yes 18423 1151.44 1024 11264
uds reliable 64 3 11.43 11.43 100.00 0 yes 0 0 1024.69 122
uds reliable 256 3 43.04 43.04 100.00 0 yes 0 0 1027 460
uds reliable 1024 3 140.24 140.24 100.00 0 yes 0 0 1032 1420
uds reliable 4096 3 464.98 464.98 100.00 0 yes 0 0 1064 4904
uds reliable 16384 3 1125.65 1125.65 100.00 0 yes 0 0 1296 11358
uds reliable 65536 3 1340.23 1331.75 99.58 2 yes 273 17.06 4096 13498

For BestEffort, accepted throughput alone can be misleading. Use received throughput, delivery rate, dropped messages/bytes, and max queued bytes together.

For Reliable, dropped message counters should normally remain zero. Failed sends indicate payloads rejected before local acceptance.

UDP Payload Smoke Summary

strategy payload send success server received client received echo matches delivery % match % timeouts
reliable 1024 1000 1000 1000 1000 100.00 100.00 0
reliable 4096 1000 1000 1000 1000 100.00 100.00 0
reliable 16384 1000 1000 1000 1000 100.00 100.00 0
besteffort 1024 1000 1000 1000 1000 100.00 100.00 0
besteffort 4096 1000 1000 1000 1000 100.00 100.00 0
besteffort 16384 1000 1000 1000 1000 100.00 100.00 0

Notes

  • No UDP payload smoke anomalies detected.

Notes

  • Full raw CSV, metadata, hardware record, manifest, and checksum are attached as release assets.
  • Latency values are round-trip local echo measurements in microseconds.
  • Strategy measurements are one-way streaming measurements.
  • UDP latency payloads above 1024 bytes were skipped for this run.
  • Jetson clocks state was not confirmed (error: Error: Run this script(/usr/bin/jetson_clocks) as a root user); interpret latency and tail values with clock/throttling caution.
  • Environment collection completed with non-fatal unavailable/error fields; see hardware.json.