Files
photoanalyzer/delivery_backlog/stories/US07-06-performance.md

941 B

US07-06 — Validate Performance and Resource Bounds

Epic: E07

As an operator, I want measured performance and bounded resource use so large libraries remain responsive and do not exhaust memory, disk, handles, or queues.

Acceptance criteria

  • Agreed budgets cover API latency, throughput, RSS, open files, WAL, queues, cache, disk reserve, and event delivery at 25k, 100k, and 500k synthetic assets.
  • Duplicate clusters with thousands of members remain usable and paged.
  • Multi-hour work plus browsing, cancellation, retry, backup, and cache eviction shows no unbounded growth or starvation.
  • Budget exceptions are measured, documented, and approved before release.

Automated tests

  • Repeatable load/soak commands export machine-readable metrics and fail budget breaches.
  • CI runs a short profile; scheduled infrastructure runs the full soak matrix.

Dependencies

  • US07-04, US07-05