SocketCluster / SocketCluster/socketcluster
Optimize for large number of subscribers
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 6.2k
- Forks
- 318
- PR merge metrics
- No merged PRs in 30d
Description
This applies to a scenario when there are a large number of subscribers (sometimes even with a small number of published messages).
When a large number of clients are subscribed to a channel, each time a message goes out, the channel can struggle to deliver the outbound messages to each subscriber and this may cause the sockets to time out and become disconnected.
Maybe we can come up with a strategy so that messages are spread out more evenly so that they don't clog up the Node.js event loop (i.e. don't try to deliver all of them in a single tick).
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
The issue does not name files, tests, or an entry point. Start by tracing channel publish delivery and Node.js event-loop behavior; done means large subscriber fan-out no longer causes socket timeouts while messages are delivered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- backend, distributed-systems, performance
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100