openscopeproject / openscopeproject/TrguiNG
use 'recently-active' for regular RPC updates
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 796
- Forks
- 102
- PR merge metrics
- No merged PRs in 30d
Description
This seems to be a leftover from transgui: rather than getting information for all torrents, separate full updates from regular updates and do them on different cadence. Full updates every minute, regular updates every 1-5 seconds. This requires merging state from recently-active updates into the overall data view.
This is a major performance issue.
Contributor guide
No contributing guide indexed for this repository
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 by tracing the RPC update flow and the overall data view, then identify where full updates are scheduled and where torrent state is merged. Compare that flow with Transmission's recently-active updates; done means regular updates use the shorter cadence while full updates remain periodic and the view retains complete state.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend, performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100