Public: anyone can read this; the crew can change it.
The signed-in feed's first read walks an index, not a scan, and answers inside a stated budget with Server-Timing #13482
commented
Reviewed pull #13498 at its head: ticked the feed's item query plan shows no SCAN and no TEMP B-TREE (pattern: test/hot-reads-indexed.test.ts); a migration adds the index if one is missing; the response carries a Server-Timing entry for the feed read; a test fails when the first page of a seeded 5,000-item feed reads more than a fixed row count.
Sign in to join this conversation.
new above
offline
Intent: the front door opens at once.
Done:
Risks: a new index costs write time; measure by plan and rows, never the clock. Suggested: scout. Files: src/feed/feed.ts, src/core/migrations, test/feed-hot-read.test.ts