Question
Handle 50000 concurrent connection
- Posted April 16, 2014
I have a static site. The site would have just some javascript and static content. I need to handle about 50,000 concurrent visitors. Can anybody explain which kind of architecture and technology is needed (e.g. single server / ngnix load balancing / …)
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
@roby <br> <br>It’s hard to make generalizations. The best thing to do would be to spin up some droplets and do some load testing of your set up. Consider throwing something like Varnish up in front of nginx to do some caching.
50000 is the highest amount of connection at one specific time, Average concurrent connection will be lower. <br> <br>Tnx
Are you sure you will be getting 50000 concurrent connections? That equals approx. 129,600,000,000 connections per month. <br> <br>Nginx works pretty well for static websites, you can start off with a 2GB droplet (in order to get 2 CPU cores) and scale up if needed. Make sure you set nginx to use 2 worker processes (<code>/etc/nginx/nginx.conf</code>). <br> <br>If you won’t be getting that amount of traffic, a 512MB droplet will do just fine.
When I run " netstat -an | grep :80 | wc -l " I get 5k - 22k on a single $5 droplet and i have 5 droplets shielded under cloudflare to load balance all my spark traffics.
my current server setup nginx->varnish->cloudflare->users
Yes, It is true I needs to setup a better $5 droplet that able to handle 50K connection in a real time and it is unhealthy for a web server to reach its maximum and unstable.