eb4bab0b90
assignDailyQuestion and aggregateOutcomeStats previously did an unbounded
db.collection('couples').get() (loading every couple into memory), and aggregate did a
serial outcomes.get() per couple (O(couples) round-trips). Both now paginate the couple
scan (orderBy __name__ + startAfter, 300/200 per page — no custom index needed):
- assignDailyQuestion: each page's create() writes fan out with the burst bounded to a page
instead of all couples at once; ALREADY_EXISTS stays the idempotent no-op.
- aggregateOutcomeStats: reads each page's outcomes in parallel instead of serially.
couples.length still counts every couple, so the aggregate windows + totalCouples are
unchanged (pure aggregate() helper and its tests untouched).
This is the one behavior-touching improvement flagged in the plan; the 512MiB/300s resource
options from B2 remain the safety net. Build clean; 70 tests green. dist rebuilt.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
||
|---|---|---|
| .. | ||
| assignDailyQuestion.js | ||
| assignDailyQuestion.js.map | ||
| assignDailyQuestion.test.js | ||
| assignDailyQuestion.test.js.map | ||
| onAnswerRevealed.js | ||
| onAnswerRevealed.js.map | ||
| onAnswerWritten.js | ||
| onAnswerWritten.js.map | ||
| onMessageWritten.js | ||
| onMessageWritten.js.map | ||