fix: batch story item counts in list_stories to eliminate N+1#663
fix: batch story item counts in list_stories to eliminate N+1#663neuron-tech-ai wants to merge 1 commit into
Conversation
list_stories() previously executed one COUNT(story_items) query per story in a Python loop. With N stories that is N+1 round-trips to SQLite regardless of list length. Replace with a single aggregated GROUP BY query that fetches all counts at once, then populate each StoryResponse from a dict lookup.
|
Warning Rate limit exceeded
You’ve run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
1 participant
list_storieswas issuing oneCOUNTquery per story to get item counts — O(n) database queries for a page of n stories. On large libraries this caused noticeable latency on every page load of the stories list.Replaced with a single
GROUP BYquery that fetches all counts in one round trip. Straightforward fix, meaningful speedup at scale.