Central speed
Median milliseconds per million completed messages across retained samples, paired to the baseline from the same round.
Latency per million messages
Profile benchmark results
Raw, Fast, and Guarded share a comparable plaintext lane. Assured runs in a separate mutually authenticated TLS lane. Each displayed value must come from accepted clean records with matching semantics and provenance.
Comparable profile state
Each row keeps its exact OS, architecture, Node version, transport lane, and commit cohort. Assured remains a separate mutual-TLS lane.
Loading compact benchmark data…
| Profile | Lane | Milliseconds / 1M | Throughput |
|---|---|---|---|
| Raw | Plaintext | Pending | Pending |
| Fast | Plaintext | Pending | Pending |
| Guarded | Plaintext | Pending | Pending |
| Assured | Mutual TLS | Pending | Pending |
Pending is not zero.
The compact dashboard could not be loaded, so this page invents no value. Rankings and certification remain disabled.
How to read an accepted result
Latency distribution
One-message-in-flight p50, p95, and p99 values from the separate latency pass.
Wire accounting
Actual sent, reflected, and received byte totals plus exact message sequence and payload verification.
Always filter by OS, architecture, Node version, transport lane, payload, commit, and oracle before comparing values. Open the raw run records for those fields.
What the profiles represent
