4 ms·
So, 502. Can you please (seriously) write a post about what your server setup is and what its like to be deal with the rush of traffic. I'll be doing it one day
by ldar15 15y ago
So, 502. Can you please (seriously) write a post about what your server setup is and what its like to be deal with the rush of traffic. I'll be doing it one day soon and all the info I can get would really help!
- dschobel 15y agoUmmmm, he may not be the best person to ask...
- notJim 15y agoFailure is the best way to learn! I know because I do so much of it! And bonus if it's someone else's failure.
- alexbosworth 15y agoSorry I'm not sure what happened - it seems like screen died?
- jat850 15y agoGoogle "node.js upstart" - there are a lot of good examples on how to get your app to respawn after crashes, run on startup, etc.
- jhuckestein 15y agoLaunching a product that's running in a screen session. I don't think it's a good idea, but I can't help but feel impressed in some way I don't understand.
- alexbosworth 15y agoThe issue was pretty mundane, the server script is very simple - so I assumed it wouldn't need to have a lot of monitoring overhead to deal with traffic spikes. Even though it's a very simple script the volume of traffic used up all the memory on the machine leading to server death, then my restart script turned out to be wrong :(
- jscheel 15y agoCheck out cluster for node.js. It will automatically create worker processes and restart them as needed. The use upstart, monit, etc to keep the master node process running.