Optimising connections per second #797
v-flashpoint
started this conversation in
General
Replies: 3 comments 2 replies
|
SSL handshake is CPU expensive, you are running on |
2 replies
|
300 per second sounds pretty reasonable (I think?). SSL handshakes are seriously CPU-intensive. |
0 replies
In which case, what would be your recommended approach for queuing upgrade requests? Sudden bursts of traffic seeing up to 1000s of req/s can be a pain to deal with as it seems to cause socket connections to hang. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hi all,
I'm using uWebSockets.js to run a quiz platform. Due to the nature of the beast, most people are only going to connect in the minutes/seconds running up to the quiz, so I've been trying to optimise the number of clients we can get connected per second.
We're using SSL (as I don't know a way to get around it from a HTTPS site!), and in testing at the moment we've been able to connect 300 clients every second on an m5a.2xlarge on AWS. The only thing we do on connecting a client is make a call to redis to get that player's information - there's very little in the way of expensive logic happening in our benchmark demo. At a rate of 300 clients per second, node is using almost 100% of its core.
What I was wondering was, is there anything we can do to optimise how quickly we can open new connections? In a best case scenario, how many connections per second should we be expecting (are there any benchmarks I've missed)?
Thanks!
All reactions