Allow more websocket connections

Posted by Switz on Server Fault See other posts from Server Fault or by Switz
Published on 2012-09-13T03:30:38Z Indexed on 2012/09/13 3:41 UTC
Read the original article Hit count: 143

I want to load balance my node.js (DerbyJS to be specific) application on a basic Linode (512MB ram). It can probably take more than one process running at once. The querys/database does not concern me as I'm not doing anything intensive. The problem at the moment is that it can only handle up to ~40 websocket connections at once. I would love if I could get that number in the few hundred+ range. I anticipate a lot of traffic on launch due to the fact that it's a highly niche community with an engaged audience, but after it should be fine with just ~20-40 connections at once, which it handles perfectly as of now. I don't mind spending a bit of money for a week or two worth of running, but I also don't want to switch production environments.

How can I test the process to see how many instances I am able to run on the box?

Will increasing the number of processes increase the amount of websockets I can handle, or is that a limitation of the server's network?

I have an old Macbook Pro running Linux sitting next to me that has 2GB ram and a 2.8 Dual Core Processor. Could I use this to handle some of the extra load? I could probably load balance with nginx to its IP. I'm on a FiOS home network.

If you have any suggestions, I'd really appreciate it. Thanks

© Server Fault or respective owner

Related posts about load-balancing

Related posts about node.js