p1-data-table-fetch-performance

drafttype/backlog

Backlog: Data table fetch performance

TL;DR

Improve Claim list / data-table loads before 2026-05-19 by cutting fetch latency, payload size, and tightening query patterns (likely overlaps stress-test performance work).

Description

  • Problem: Slow or heavy data-table fetches hurt UX and may contribute to load issues under concurrency.
  • Scope: Pagination, selected columns, N+1 / over-fetching, indexes, API batching, caching where appropriate.
  • Context: Related backlog: stress test failure under 500 VUs — align findings so fixes do not conflict.

Acceptance Criteria

  • Baseline: document current worst-case table route (query count, payload KB, p95 latency) in staging or prod-like env
  • Change set merged with measured improvement (target: agreed p95 / payload budget) or documented tradeoff
  • Linked notes / PR references for any schema or index change

Priority

  • Priority: p1
  • Rationale: Time-boxed (next Monday); table fetch is a primary operator surface.

Dependencies

  • Blocks: —
  • Blocked by: —
  • Related: [[Projects/anabatic-claim/backlog/p1-stress-test-performance-failure]]

Links

  • Project context: [[Projects/anabatic-claim/context/index]]
  • Hub: [[Projects/anabatic-claim/anabatic-claim]]

Notes

  • Originated from inbox triage 2026-05-16.