SocketCluster / SocketCluster/socketcluster
Callbacks scale much more than async/await approach
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 6.2k
- Forks
- 318
- PR merge metrics
- No merged PRs in 30d
Description
I had done some extensive testing, I had some observations ->
- The older approach that socket cluster offered (v14.2) scales much better as compared to the new async/await approach. ( i had too many subs pubs every seconds, around 2k connects+disconnects and around 5k messages published every second)
Refer to event loop added below
The event loop is not able to handle when we have around 30k average connections with the above mentioned condition, whereas same works amazingly well with 14.2 version.
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 reproducing the comparison between the v14.2 callback approach and the newer async/await approach under the reported load: about 30k connections, 2k connects/disconnects per second, and 5k published messages per second. Compare event-loop behavior and determine what changed; done requires an identified cause and a verified improvement against the v14.2 baseline.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- backend, networking, performance
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100