Replying to Avatar Alex Gleason

>how many concurrent clients you support

At least 1,048,576.

You will most likely hit filesystem limits of the OS before you hit network or memory limits. Keeping an idle websocket open uses basically no CPU. And if you're just punting off their requests to some database, even active connections won't hit CPU limits of modern equipment. Your database on the other hand...
Avatar
Tim Bouma 11mo ago

lol. My service is being designed to support up to 4,294,967,296 unique clients, though I don’t think I’ll be able to convince half the world’s population to use a single service instance.

Good info on the websockets. Thx.

Reply to this note

Please Login to reply.

Discussion

Avatar
Alex Gleason 11mo ago

If you get to that point, just run multiple servers, and use some DNS tricks to get traffic routed to different servers based on the user's location.

Avatar
Tim Bouma 11mo ago

Yup.

I’ve architected everything so that I can take advantage of that cool infrastructure stuff. Already in discussions with an ops friend that does this for a living.