Recommended Targets
The cards are sorted by total score for this run. Each card is one tested URL or transport configuration; open it to see the URL, run mode, best and weakest latency cases, throughput, CPU, and counted cases.
Total score is out of 120. Higher is better for the current test mix. Sub-pills show: latency / throughput / resource / coverage / delivery / send-block. The "Recommended Targets" headline shows the strongest URL for this run.
Total score formula (max 120)
- Latency 30% — Subscriber-side end-to-end latency. Per case we weight P95×0.70 + P99×0.25 + P99.9×0.04 + P99.99×0.01 through a payload-aware curve, then use an equal-weight geometric mean across cases.
- Throughput 20% — recv MB/s on the subscriber side, log-scaled vs 1024 MB/s reference. Higher throughput → higher score.
- Resource 10% — throughput per unit CPU. Lower CPU at the same throughput → higher score.
- Delivery 10% — Aggregated loss across all cases: avg_delivery = 100 - loss%. Loss > 5% also lightly cuts per-case latency via a logistic curve (gentle ≤20%, accelerates >20%, capped at ×0.40) to defeat survivor-bias.
- Send-block 10% — wall-clock time spent inside publish() per message (P99), equal-weight across latency/backpressure cases. Penalizes APIs that block the publisher thread.
- Coverage 10% — Passing cases / total cases for this URL. Standalone dimension; also serves as fallback for the topology slot when topology suite is absent.
- Topology 10% — Topology suite roll-up (1:n / n:1 / n:n). Falls back to clamp(coverage, 60, 95) when topology suite was not run.
total = (0.36·latency + 0.24·throughput + 0.12·resource + 0.12·delivery + 0.12·send-block + 0.12·coverage + 0.12·topology) · confidence_factor
Confidence is derived from aggregate/worst-case loss% and latency sample drops: <5% high, <15% medium, ≥15% noisy; solo means no peers, unknown means all cases failed. Multipliers: high 1.00 / solo·medium 0.99 / unknown·noisy 0.95.
Top recommendation: shm:// total 117/120
It is the strongest result in this run; use latency, throughput, and Transport Health below to confirm details.
#1shm://cross-process⚡ Latency score 98📦 Throughput score 100🔋 Resource score 100🎯 Coverage score 100📦 Delivery score 100🔒 Send-block score 85total 117conf high
shm://cross-process⚡ Latency score 98📦 Throughput score 100🔋 Resource score 100🎯 Coverage score 100📦 Delivery score 100🔒 Send-block score 85total 117conf highprotocol/transport
shm://URL
shm://bench/perf_shm?depth=10run modecross-process
best P95 latency21.4 us@ 128 B / 1000 Hz
weakest latency case93/100@ 128 B / 1000 Hz, P95 21.4 us, P99.9 338.8 us
peak received throughput11210.9 MB/s@ 256 KB
avg CPU117.2%publisher + subscriber
best send-block P995.26 us@ 16 KB
loss rate0.133%across all cases
counted runs8
#2dds://cross-process⚡ Latency score 78📦 Throughput score 86🔋 Resource score 33🎯 Coverage score 100📦 Delivery score 71🔒 Send-block score 32total 84conf noisy⚠ Loss 33.202%
dds://cross-process⚡ Latency score 78📦 Throughput score 86🔋 Resource score 33🎯 Coverage score 100📦 Delivery score 71🔒 Send-block score 32total 84conf noisy⚠ Loss 33.202%protocol/transport
dds://URL
dds://bench/perf_dds?qos=betterrun modecross-process
best P95 latency47.2 us@ 128 B / 1000 Hz
weakest latency case51/100@ 2 MB / 1000 Hz, P95 2294.3 us, P99.9 2357.8 us
peak received throughput1349.0 MB/s@ 1 MB
avg CPU139.7%publisher + subscriber
best send-block P9925.60 us@ 128 B
loss rate33.202%across all cases
counted runs8
#3ddsc://cross-process⚡ Latency score 52📦 Throughput score 76🔋 Resource score 25🎯 Coverage score 100📦 Delivery score 95🔒 Send-block score 34total 75conf noisy⚠ Loss 75.855%
ddsc://cross-process⚡ Latency score 52📦 Throughput score 76🔋 Resource score 25🎯 Coverage score 100📦 Delivery score 95🔒 Send-block score 34total 75conf noisy⚠ Loss 75.855%protocol/transport
ddsc://URL
ddsc://bench/perf_ddsc?qos=betterrun modecross-process
best P95 latency35.7 us@ 128 B / 1000 Hz
weakest latency case7/100@ 2 MB / 1000 Hz, P95 4755.3 us, P99.9 5212.3 us
peak received throughput1352.4 MB/s@ 256 KB
avg CPU157.2%publisher + subscriber
best send-block P9924.29 us@ 128 B
loss rate75.855%across all cases
counted runs8
Run Overview
Samples
24
Planned Cases
24
Skipped Cases
0
Cases
24
Passing
20
Warning
4
Failing
0
Repeated runs of the same case are merged; averages only count successful runs. Delivery loss is shown once it reaches 5% so trace amounts of normal jitter do not distract from the main result.
Metric Guide
Terminology used throughout the report. Skim it once and the recommendation, heatmaps, and category results below all become easier to interpret.
| Metric | Meaning |
|---|---|
| P50 / P90 / P99 latency (and P99.9 / P99.99 in detail tables) | Latency percentiles. The heatmap shows P50 (typical), P90 (slower common case), and P99 (tail) side by side; detail tables also include P99.9 and P99.99 to surface rare slow messages. Lower numbers are better across the board. |
| Received MB/s | How many megabytes per second the subscriber actually received. This is the main throughput number. |
| Loss ratio | Messages that were expected but not received. Small loss can happen in stress tests; the report only highlights loss at 5% or higher, and marks very high loss more strongly. |
| Confidence | A quick read on result reliability, based on run success, visible loss, and latency sample drops. Low confidence means review Transport Health and problem cases; final judgment still depends on latency and throughput. |
| Message size / payload | The size and type of each message sent during the test. Larger messages usually stress bandwidth, buffers, and copying more. |
| Connection topology | The publisher/subscriber shape, such as 1:1, 1:n, n:1, or n:n. It shows whether a transport scales when more senders or receivers are involved. |
| CPU Efficiency | How much throughput is achieved for the CPU used by publisher and subscriber. It helps break ties, but latency and throughput remain the main decision signals. |
Transport Health
warnings
Transport Health tells whether this report is trustworthy before you compare scores. It summarizes failed cases, warnings, URL coverage, and problem cases. Green means no obvious problem; yellow means review loss, skipped, or unstable results; red means inspect the problem-case error first. Small loss is still recorded; this section highlights loss, failures, or skips that may affect the conclusion.
| Transport | Mode | Problem Cases | Total Cases |
|---|---|---|---|
shm | process | 0 | 8 |
dds | process | 1 | 8 |
ddsc | process | 3 | 8 |
Tested URL Coverage
| Transport | URL | Modes | Passing | Warning | Failing | Best Recv MB/s | Best P95 us |
|---|---|---|---|---|---|---|---|
shm | shm://bench/perf_shm?depth=10 | process | 8 | 0 | 0 | 11210.88 | 21.45 |
dds | dds://bench/perf_dds?qos=better | process | 7 | 1 | 0 | 1349.00 | 47.15 |
ddsc | ddsc://bench/perf_ddsc?qos=better | process | 5 | 3 | 0 | 800.38 | 35.67 |
Cases to Review
| Category | Mode | Transport | Payload | Config | Repeats | Status | Errors |
|---|---|---|---|---|---|---|---|
| throughput | process | dds | bytes / 16 KB | url: dds://bench/perf_dds?qos=bettertopology: 1:1 [1p/1s]pattern: max | 1/1 | WARN 1/1 loss | |
| throughput | process | ddsc | bytes / 256 KB | url: ddsc://bench/perf_ddsc?qos=bettertopology: 1:1 [1p/1s]pattern: max | 1/1 | WARN 1/1 loss | |
| throughput | process | ddsc | bytes / 1 MB | url: ddsc://bench/perf_ddsc?qos=bettertopology: 1:1 [1p/1s]pattern: max | 1/1 | WARN 1/1 loss | |
| latency | process | ddsc | bytes / 2 MB | url: ddsc://bench/perf_ddsc?qos=bettertopology: 1:1 [1p/1s]pattern: fixed | 1/1 | WARN 1/1 loss |
Latency / Throughput
Latency by Message Size (P50 / P90 / P99, lower is better)
Each cell has three bars: P50 / P90 / P99 (left to right), shorter and greener is better. Numbers on the right follow the same order, in µs. Blank = no data, FAIL = case failed.
low latencymedium latencyhigh latency
test target \ message size
128 B
4 KB
64 KB
512 KB
2 MB
shm://process | shm://bench/perf_shm?depth=10P5015.0us
P9021.0us
P9924.8us
100/100P5020.7us
P9021.8us
P9930.2us
100/100P5038.0us
P9040.3us
P9949.0us
100/100P5069.8us
P9073.0us
P99144us
100/100P50484us
P90507us
P99536us
100/100dds://process | dds://bench/perf_dds?qos=betterP5029.1us
P9046.0us
P9949.7us
100/100P5048.2us
P9049.5us
P9998.2us
91/100P5081.7us
P9086.4us
P99113us
97/100P50383us
P90443us
P99469us
76/100P501934us
P902273us
P992325us
54/100ddsc://process | ddsc://bench/perf_ddsc?qos=betterP5028.9us
P9034.8us
P9939.0us
100/100P5035.2us
P9038.9us
P9943.9us
100/100P5092.3us
P90103us
P99113us
97/100P50496us
P90645us
P99695us
57/100P501935us
P904725us
P994869us
19/100Throughput by Message Size (received MB/s, higher is better)
This chart uses throughput tests only. Each row is one test target and each column is a message size. The number is mean received MB/s. Longer greener horizontal bars mean the subscriber actually received more data. Blank or failed cells have no valid result.
test target \ message size
16 KB
256 KB
1 MB
shm://process | shm://bench/perf_shm?depth=105520 MB/s100/100
11211 MB/s100/100
9840 MB/s100/100
dds://process | dds://bench/perf_dds?qos=better805 MB/s48/100
1114 MB/s50/100
1349 MB/s69/100
ddsc://process | ddsc://bench/perf_ddsc?qos=better800 MB/s48/100
1352 MB/s54/100
413 MB/s43/100
Category Results
This table lists the best configuration in each test category. Different categories focus on different signals, so compare scores inside the same category.
| Mode | Category | Best Result | Score | Coverage | Conclusion |
|---|---|---|---|---|---|
process | latency | shm://process | shm://bench/perf_shm?depth=10 | 98.5 | 5/5 case(s), 100.0% repeat success, 1 url(s) | Lowest latency: P95 134.96 us, P99 156.95 us, P99.9 337.21 us, P99.99 835.94 us. |
process | throughput | shm://process | shm://bench/perf_shm?depth=10 | 100.0 | 3/3 case(s), 100.0% repeat success, 1 url(s) | Best throughput: received 8856.82 MB/s, first message 0.66 ms. |
This table scores throughput, latency, backpressure, topology, and serialization separately. Compare scores inside the same category; a latency score and a throughput score are not interchangeable.
Each score is mainly driven by the most important metric for that category, with a small health check for failures, visible loss, latency sample drops, and repeat success.
| Category | What is scored | How to read it | Best used for |
|---|---|---|---|
throughput | Mainly received MB/s, with small checks for send/receive efficiency and health. | Throughput tests mainly answer how much data was actually received. Health only highlights clear problems. | Useful for choosing the configuration that carries more data under larger payloads or heavier send pressure. |
latency | Mainly P95/P99 latency quality, with light tail-stability checks for P99.9/P99.99, max latency, jitter, throughput, and health. | Latency tests mainly use percentiles. The heatmap visualises P50 (typical) / P90 (slower common case) / P99 (tail). P99.9 / P99.99 stay visible as tail-stability signals, but they do not dominate the score. Lower numbers are better. | Useful for checking whether messages respond quickly and whether slow-message latency stays controlled. P95/P99 drive the score, while P99.9/P99.99 help explain rare stalls. |
backpressure | Mainly publisher-side P99 send-block time, with checks for delivered throughput, send/receive efficiency, and health. | Backpressure tests simulate slow consumers. Lower publish() blocking time is better, but the run still needs to deliver messages reliably. | Useful for spotting transports that stall publisher threads when subscribers fall behind. |
topology | Mainly total received MB/s and scaling efficiency, with small checks for send/receive efficiency and health. | Topology tests mainly check whether total throughput keeps up as publishers or subscribers increase. | Useful for one-to-many, many-to-one, and many-to-many deployment shapes. |
serialization | Mainly encode/decode speed, also checking coverage, repeat success, efficiency, balance, CPU, and memory. | Serialization mainly compares encode/decode speed and checks repeat stability. | Useful for judging data-format cost. It does not represent the full communication path. |
Result Highlights
This run covers 3 url(s), 3 transport(s), and 1 mode(s). normal cases: 20/24; problem cases: 4.
The most normal cases come from
shm in process mode with 8 normal case(s).This section highlights the easiest results to notice in this report: highest throughput, lowest latency, topology scaling, and fastest encode/decode. Use it to find leads quickly, then confirm with the recommendation, heatmaps, and problem cases.
Highest 1:1 throughput:
shm | process | 1:1 [1p/1s] | bytes | 256 KBreceived 11210.88 MB/s | first msg 0.48 ms | repeats 1/1
url:
shm://bench/perf_shm?depth=10Lowest 1:1 latency:
shm | process | 1:1 [1p/1s] | bytes | 128 Bp95 21.45 us | p99 24.82 us | received 0.12 MB/s | repeats 1/1
url:
shm://bench/perf_shm?depth=10Transport Summary
Groups each URL/transport configuration into one row for a quick trend view. A row can include multiple message sizes, rates, or topologies, so use latency/throughput comparisons and trend charts for exact comparisons.
Groups results by transport type, run mode, and test category for a quick trend view. Because a row can include multiple message sizes or rates, use latency/throughput comparisons and trend charts for exact comparisons.
| Transport | Mode | URL | Category | Score | Coverage | Mean Received MB/s | Mean Run P95 us | Loss % | Mean Peak RSS MB |
|---|---|---|---|---|---|---|---|---|---|
shm | process | shm://bench/perf_shm?depth=10 | latency | 98.5 | 5/5 | 100.0% repeat | 513.31 | 134.96 | - | 39.0 |
dds | process | dds://bench/perf_dds?qos=better | latency | 79.2 | 5/5 | 100.0% repeat | 314.31 | 588.51 | - | 42.7 |
ddsc | process | ddsc://bench/perf_ddsc?qos=better | latency | 66.7 | 5/5 | 100.0% repeat | 237.51 | 1122.10 | 61.925 | 42.0 |
shm | process | shm://bench/perf_shm?depth=10 | throughput | 100.0 | 3/3 | 100.0% repeat | 8856.82 | - | - | 43.0 |
dds | process | dds://bench/perf_dds?qos=better | throughput | 89.2 | 3/3 | 100.0% repeat | 1089.32 | - | 33.202 | 43.0 |
ddsc | process | ddsc://bench/perf_ddsc?qos=better | throughput | 82.7 | 3/3 | 100.0% repeat | 855.25 | - | 75.855 | 42.1 |
Trend Charts
Throughput (process)
Latency (process)
Loss (process)
Send-block (process)
First Message (process)
Resource CPU (process)
Resource RSS (process)
Detail Tables
Transport Detail Table
| Category | Mode | Transport | Payload | Config | Rate | Repeats | Received MB/s | Mean P95 us | Mean P99.9 us | Send-block P99 us | Loss % | CPU % | Peak RSS MB | Status |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| throughput | process | shm | bytes / 16 KB | url: shm://bench/perf_shm?depth=10topology: 1:1 [1p/1s]pattern: max | max | 1/1 | 5519.59 | - | - | 5.26 | 0.00 | 191.92 | 44.0 | OK 1/1 |
| throughput | process | shm | bytes / 256 KB | url: shm://bench/perf_shm?depth=10topology: 1:1 [1p/1s]pattern: max | max | 1/1 | 11210.88 | - | - | 24.20 | 0.13 | 129.55 | 42.4 | OK 1/1 |
| throughput | process | shm | bytes / 1 MB | url: shm://bench/perf_shm?depth=10topology: 1:1 [1p/1s]pattern: max | max | 1/1 | 9840.00 | - | - | 80.33 | 0.00 | 108.83 | 42.6 | OK 1/1 |
| throughput | process | dds | bytes / 16 KB | url: dds://bench/perf_dds?qos=bettertopology: 1:1 [1p/1s]pattern: max | max | 1/1 | 805.22 | - | - | 26.91 | 33.20 | 222.50 | 41.8 | WARN 1/1 loss |
| throughput | process | dds | bytes / 256 KB | url: dds://bench/perf_dds?qos=bettertopology: 1:1 [1p/1s]pattern: max | max | 1/1 | 1113.75 | - | - | 263.50 | 0.02 | 153.92 | 41.9 | OK 1/1 |
| throughput | process | dds | bytes / 1 MB | url: dds://bench/perf_dds?qos=bettertopology: 1:1 [1p/1s]pattern: max | max | 1/1 | 1349.00 | - | - | 822.72 | 0.18 | 160.29 | 45.4 | OK 1/1 |
| throughput | process | ddsc | bytes / 16 KB | url: ddsc://bench/perf_ddsc?qos=bettertopology: 1:1 [1p/1s]pattern: max | max | 1/1 | 800.38 | - | - | 40.52 | 0.00 | 212.30 | 39.0 | OK 1/1 |
| throughput | process | ddsc | bytes / 256 KB | url: ddsc://bench/perf_ddsc?qos=bettertopology: 1:1 [1p/1s]pattern: max | max | 1/1 | 1352.38 | - | - | 170.13 | 22.79 | 209.06 | 39.7 | WARN 1/1 loss |
| throughput | process | ddsc | bytes / 1 MB | url: ddsc://bench/perf_ddsc?qos=bettertopology: 1:1 [1p/1s]pattern: max | max | 1/1 | 413.00 | - | - | 639.44 | 75.86 | 199.41 | 47.5 | WARN 1/1 loss |
| latency | process | shm | bytes / 128 B | url: shm://bench/perf_shm?depth=10topology: 1:1 [1p/1s]pattern: fixed | 1000Hz | 1/1 | 0.12 | 21.45 | 338.76 | 10.66 | 0.00 | 101.28 | 37.4 | OK 1/1 |
| latency | process | shm | bytes / 4 KB | url: shm://bench/perf_shm?depth=10topology: 1:1 [1p/1s]pattern: fixed | 1000Hz | 1/1 | 3.91 | 23.12 | 49.25 | 12.23 | 0.00 | 101.49 | 37.4 | OK 1/1 |
| latency | process | shm | bytes / 64 KB | url: shm://bench/perf_shm?depth=10topology: 1:1 [1p/1s]pattern: fixed | 1000Hz | 1/1 | 62.50 | 41.43 | 61.94 | 11.00 | 0.00 | 101.18 | 37.5 | OK 1/1 |
| latency | process | shm | bytes / 512 KB | url: shm://bench/perf_shm?depth=10topology: 1:1 [1p/1s]pattern: fixed | 1000Hz | 1/1 | 500.00 | 74.34 | 329.80 | 46.76 | 0.00 | 101.69 | 39.3 | OK 1/1 |
| latency | process | shm | bytes / 2 MB | url: shm://bench/perf_shm?depth=10topology: 1:1 [1p/1s]pattern: fixed | 1000Hz | 1/1 | 2000.00 | 514.47 | 906.29 | 138.19 | 0.00 | 101.28 | 43.2 | OK 1/1 |
| latency | process | dds | bytes / 128 B | url: dds://bench/perf_dds?qos=bettertopology: 1:1 [1p/1s]pattern: fixed | 1000Hz | 1/1 | 0.12 | 47.15 | 61.48 | 25.60 | 0.00 | 103.97 | 40.5 | OK 1/1 |
| latency | process | dds | bytes / 4 KB | url: dds://bench/perf_dds?qos=bettertopology: 1:1 [1p/1s]pattern: fixed | 1000Hz | 1/1 | 3.91 | 51.24 | 260.81 | 53.42 | 0.00 | 104.34 | 40.6 | OK 1/1 |
| latency | process | dds | bytes / 64 KB | url: dds://bench/perf_dds?qos=bettertopology: 1:1 [1p/1s]pattern: fixed | 1000Hz | 1/1 | 62.50 | 89.74 | 323.39 | 51.73 | 0.00 | 105.30 | 40.8 | OK 1/1 |
| latency | process | dds | bytes / 512 KB | url: dds://bench/perf_dds?qos=bettertopology: 1:1 [1p/1s]pattern: fixed | 1000Hz | 1/1 | 500.00 | 460.08 | 598.91 | 436.70 | 0.00 | 124.70 | 43.0 | OK 1/1 |
| latency | process | dds | bytes / 2 MB | url: dds://bench/perf_dds?qos=bettertopology: 1:1 [1p/1s]pattern: fixed | 1000Hz | 1/1 | 1005.00 | 2294.32 | 2357.83 | 1655.21 | 0.10 | 142.73 | 48.5 | OK 1/1 |
| latency | process | ddsc | bytes / 128 B | url: ddsc://bench/perf_ddsc?qos=bettertopology: 1:1 [1p/1s]pattern: fixed | 1000Hz | 1/1 | 0.12 | 35.67 | 46.25 | 24.29 | 0.00 | 103.18 | 36.2 | OK 1/1 |
| latency | process | ddsc | bytes / 4 KB | url: ddsc://bench/perf_ddsc?qos=bettertopology: 1:1 [1p/1s]pattern: fixed | 1000Hz | 1/1 | 3.91 | 39.43 | 50.25 | 26.08 | 0.00 | 103.22 | 36.3 | OK 1/1 |
| latency | process | ddsc | bytes / 64 KB | url: ddsc://bench/perf_ddsc?qos=bettertopology: 1:1 [1p/1s]pattern: fixed | 1000Hz | 1/1 | 62.50 | 106.83 | 132.46 | 74.48 | 0.00 | 105.75 | 39.3 | OK 1/1 |
| latency | process | ddsc | bytes / 512 KB | url: ddsc://bench/perf_ddsc?qos=bettertopology: 1:1 [1p/1s]pattern: fixed | 1000Hz | 1/1 | 500.00 | 673.28 | 890.24 | 514.41 | 0.00 | 139.27 | 42.5 | OK 1/1 |
| latency | process | ddsc | bytes / 2 MB | url: ddsc://bench/perf_ddsc?qos=bettertopology: 1:1 [1p/1s]pattern: fixed | 1000Hz | 1/1 | 621.00 | 4755.27 | 5212.26 | 1276.77 | 61.93 | 185.34 | 55.7 | WARN 1/1 loss |