Performance is a release requirement

Benchmark overview

Every result starts from a fresh process and endpoint, communicates with the same raw reflector contract, retains its samples, and reports provenance. Missing evidence stays visibly missing.

Current tracked profile state

Tracked node-ipc profile benchmark status chart
The chart shows only accepted comparable profile evidence. Pending means no clean like-for-like profile result has passed the publication gates.

Open the evidence you need

01

v12 vs recorded transports

Paired time for one million messages through native local IPC, TCP, TLS, UDP4, and UDP6 on Linux, macOS, and Windows. Every cohort names its exact measured version.

Open transport comparison →
02

Node.js ↔ Rust

The same validated TCP round trip across Node/Node, Node/Rust, Rust/Node, and Rust/Rust with exact cleanup, memory, and package evidence.

Open Rust and Node.js benchmark →
03

Profile performance

Latency per million messages, throughput, and selected-control overhead for Raw, Fast, Guarded, and Assured.

Open profile results →
04

Resources + cleanliness

Memory checkpoints, package footprint, garbage collection, process exits, socket reuse, active resources, and temporary leftovers.

Open resource results →
05

Methodology

The reflector contracts, paired order, clean baselines, instrumentation lanes, byte accounting, and publication gates.

Open methodology →
06

Tracked profile runs

Machine, OS, architecture, Node, commit, oracle, configuration, hashes, raw samples, and manifest state.

Open profile run records →

Comparison boundaries

Raw client lane

Compatible clients connect to the same byte-reflector source and protocol. Every sample receives a fresh reflector process and endpoint.

Profile lane

Raw, Fast, and Guarded are compared under the same transport and payload semantics. Their wire byte counts are measured, not assumed.

Assured lane

Assured requires mutually authenticated TLS for network use and is measured separately with its certificate, trust-root, and transport configuration recorded. It is not ranked as plaintext.

Baseline history is not a profile result.

The existing six-platform/Node records establish the standard-C oracle and publication infrastructure. They do not supply profile latency or a vehicle ranking.