krestenlaust / krestenlaust/ChessGame
Improve dangerzone calculation performance
- Dominant language
- C#
- Stars
- 5
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
- Right now, every time a single move has been made, either in a real move or a simulated move (all moves are simulated before being presented to the player), all pieces dangersquares are being recalculated.
Changing this approach to only update possibly affected pieces, should improve performance.
- Performance analysis results of bots, shows that UpdateDangerzones() is a major hot path. Any improvements should improve calculation speed of bots.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating UpdateDangerzones() and tracing how it is called after real and simulated moves, especially during bot analysis. Profile the current calculation path, then verify that only potentially affected pieces are updated and that bot move analysis completes faster without changing danger-square results.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- game-dev, performance
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100