Performance enhancements when calculating averages
Open
enhancement
- Dominant language
- JavaScript
- Stars
- 30
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Description
Right now I have a poor approach to calculating stats which is calculating everyone's after each solve. Especially when I don't use every stat that I'm calculating.
I need to somehow only calculate the stats that I need and calculate stats incrementally. This is especially with calculating best averages.
Contributor guide
Research direction
No files, tests, or entry points are identified; begin by tracing where solve results and statistics are currently calculated. Define which requested statistics need to be computed and how best averages can be updated incrementally, then verify that unused statistics are not calculated for every solve.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- performance
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100