HydraCache 0.58.0
HydraCache 0.58.0
0.58.0 is the endurance, soak, and overload-hardening release. It turns the
short deterministic simulation proof into a bounded multi-seed soak workflow,
adds resource-growth checks, and records overload behavior without turning the
release into a benchmark or throughput claim.
The release does not add a new consensus algorithm, storage engine, or
consistency level. It hardens the evidence around the shipped 0.44
simulator, the 0.46 admission/backpressure surface, and the operator/kind
test path that later networked releases build on.
Highlights
- Added a wall-clock-budgeted multi-seed soak driver over
hydracache-simso
invariant failures are reported with reproducible seed and step evidence. - Added storage-footprint/resource-growth accounting and bounded-growth checks
so leak-over-time failures can turn the release gate red. - Added sustained-overload proof around the shipped admission controller:
bounded in-flight work, bounded memory accounting, counted rejects, and
recovery-after-overload behavior. - Added a structured
SOAK_REPORTshape for nightly/pre-release evidence. The
report records seeds, budget, invariant status, and bounded-resource verdicts
without publishing a numeric self-score. - Added the bounded soak gate beside the existing DST fast-budget gate so the
release proof is executable instead of prose-only. - Re-scoped the live multi-node chaos evidence honestly: later networked daemon
releases upgrade the target from an operator fixture to the real networked
daemon grid.
Verification
Representative release gates:
cargo test -p hydracache-sim --test dst_budget --locked
cargo test -p hydracache-sim --test soak_budget --locked
cargo run -p hydracache-sim --bin vopr --locked -- soak --master-seed 22530 --budget-secs 60 --steps-per-seed 512 --max-seeds 128
cargo xtask verifyExtended pre-release tiers remain environment-gated when they require a live
cluster, Kubernetes, Docker, or process-level fault injection.
Scope Boundary
This is an evidence and hardening release, not a promise of production mileage
equivalent to years in the field. The embedded cache fast path remains
unchanged; soak failures are seeds and reports to investigate, not throughput
marketing.