SocketCluster / SocketCluster/socketcluster
Improve performance by avoiding setTimeout
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 6.2k
- Forks
- 318
- PR merge metrics
- No merged PRs in 30d
Description
Right now a lot of features of SC rely on setTimeout (like when an emitted event expects a response from the opposite socket or as part of ping/pong).
Maybe this should be handled differently (e.g. using a low precision timer).
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
No files, tests, or entry points are named. Trace the setTimeout uses for emitted-event responses and ping/pong, then investigate the proposed low-precision timer approach. Done is not defined beyond improving performance without breaking those behaviors, so the scope needs maintainer clarification.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- networking
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100