Performance And Caching

V1 keeps PostgreSQL as the required storage and cache dependency. Redis is intentionally deferred.

Hot paths

• Dashboard recent scans and score summaries.
• Scan detail score and coverage summaries.
• Issue page first load.
• Issue detail pagination.
• PDF, CSV, and LLM report startup.

Rules of thumb

Do not rebuild a full issue list in memory to render the first page. Keep occurrence detail live and paginated. Persist derived summaries where repeated aggregation would be expensive.

Invalidation

Refresh or invalidate cached data after scan completion, same-scan retry completion, false-positive changes, scan deletion, and settings changes that alter report output shape.