Skip to content

ringfire 0.5.2 — verified benchmarks and 95% coverage gate

Choose a tag to compare

@alex09x alex09x released this 27 Sep 03:27
· 9 commits to main since this release
0f738ca

ringfire 0.5.2 corrects benchmark methodology and makes test coverage a CI requirement.

  • Production Rust line coverage above 95%: 96.67% measured on Linux AArch64 and 96.47% on GitHub Linux x86-64, including CLI, FFI, Tokio and replication. Tests are excluded from the denominator; production modules are included. CI runs on Linux x86-64 and AArch64 and publishes JSON/HTML reports.
  • Receive benchmarks now time successful validated receives, with refill outside the timer and correct batch accounting. IPC compares full 64-byte replies uniformly and separates adaptive futex from zero-spin waiting. Every harness has bounded execution and isolated temporary files.
  • Network examples report distinct-message losses, duplicates and ordering, keep warm-up counters separate, and fail on transport/clock-probe errors. Local and round-trip stage measurements use a monotonic clock.
  • The multiprocess stress test now proves that eight child readers each consume and validate all 100,000 records. Added behavioral CLI/FFI, malformed-input, asynchronous and replication recovery tests.
  • New finite CLI modes: top --iterations N and TCP serve --once. Existing long-running behavior and signal semantics remain unchanged.
  • README charts and tables use three repeated measurements of all 28 Criterion cases; raw samples and machine settings are included. Historical invalid receive figures are withdrawn. Historical LAN/WAN results remain explicitly labelled and were not remeasured.

Benchmark methodology · All measurements and raw samples · Coverage contract

The 95% gate is line coverage, not exhaustive branch or concurrency coverage. The ARM measurements ran on a shared host; every repeat and its range is retained. Wire formats remain compatible with v0.5.x.

Closes #6 via #7.