Dev Task: Performance bug, N+1 Query
Open
4Refinement
Bug
- Dominant language
- Python
- Stars
- 65
- Forks
- 11
- Avg merge
- 21h 25m
- Merged PRs (30d)
- 70
Description
Sentry Issue: [BACKEND-3T](https://bcps-wps.sentry.io/issues/6328708667/?referrer=github_integration)
| | |
| ------------- | --------------- |
| **Offending Spans** | db - SELECT DISTINCT ON (advisory_fuel_stats.fu...
Contributor guide
Research direction
Start with the linked Sentry issue and inspect the reported database SELECT spans for the source of the N+1 query. Identify the backend entry point responsible, reproduce or profile the request, and confirm completion when the repeated queries are removed and the database spans show the expected performance improvement.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql, python
- Domain
- backend, database, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100