Internal scoreboard is completely nonfunctional in large competitions
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1k
- Forks
- 412
- Avg merge
- 6d 10h
- Merged PRs (30d)
- 3
Description
In CMS Admin, rendering the internal ranking page for several hundred contestants across multiple tasks suffers from severe latency and frequent request timeouts. I believe this is caused by synchronous, non-cached score calculations.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the CMS Admin internal ranking page and reproduce the timeout with a competition containing several hundred contestants and multiple tasks. Profile the synchronous score-calculation path and verify that the page renders within an acceptable time without request timeouts for that workload.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100