Skip to main content
The memvid-core Dev Steps require a crash harness that runs 1 000 cycles of mutate/crash/recover with zero data loss.

Harness expectations

  • Randomly ingest frames, call commit() at varied intervals
  • Kill the process mid-commit to leave partial WAL writes
  • Restart, let Memvid::open() replay the WAL, and assert:
    • frame_count matches expectations
    • timeline() returns ordered timestamps (verifies Time Index Track persisted)
    • Checksums match (header, TOC, time index)

Sample assertion

Performance target - open_and_recover_latency must stay below 250 ms, even when replaying WAL entries (Security & Performance Architecture).