Benchmarks

The Rust benchmarks live as executable binaries under src/bin/.

The benchmark map is maintained in ../BENCHMARKS.md. It includes the latest recorded release-mode run: this-me v0.3.0 Run #001 from Aug 26, 2026 on Suis-MacBook-Air.local.

The Rust-vs-TypeScript mirror suite is documented in ../BENCHMARK_COMPARISON.md. Run #002 records the source-versioned lazy invalidation fix.

Run benchmarks in release mode:

cargo run --release --bin bench-ok
cargo run --release --bin bench-sustained
cargo run --release --bin bench-fanout
cargo run --release --bin bench-cold-warm
cargo run --release --bin bench-explain-overhead
cargo run --release --bin bench-secret-scope
cargo run --release --bin bench-push-pull
cargo run --release --bin bench-secret-push-pull
cargo run --release --bin bench-mirror

Coverage:

• O(k) recompute isolation,
• sustained mutation,
• fan-out sensitivity,
• cold vs warm hydration,
• explain() overhead,
• secret scope cost,
• eager vs lazy recompute,
• secret push vs pull.

Benchmarks are not hard regression thresholds yet. They are measurement tools for keeping the Rust port honest while it catches up to the TypeScript kernel.

The current runs confirm the important shape: irrelevant memory stays out of small recompute waves, sustained mutation does not drift upward, hydration is a startup cost, and lazy writes no longer walk every subscriber at mutation time.

The rule: improve mechanics, but do not change .me meaning to chase a number.