Improve kci-summary API performance
Open
Backend
Queries
- Dominant language
- Python
- Stars
- 9
- Forks
- 31
- Avg merge
- 3d 19h
- Merged PRs (30d)
- 16
Description
Discussed approaches without migrating the database:
- [ ] Limit the query by checkout numbers instead of days?
- [ ] Get history and summary and execute everything in python
On hold until we check for performance improvements with the database replica
Contributor guide
Research direction
The issue names the kci-summary API but no files or tests; first check performance improvements with the database replica, then evaluate the proposed checkout-number query and Python history-and-summary approaches without migrating the database. Done means selecting and implementing an approach with measurable performance improvement, though no target is specified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend, performance
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100