My, how things have changed since the C10k problem... http://www.kegel.com/c10k.html
The C10k solutions are effectively the same as for C500k, those being epoll (Linux), kqueue (BSD), etc. Our Java NIO server utilizes epoll to handle C500k.
Linux Kernel Tuning for C500k
21–26 of 26 posts
Re: Linux Kernel Tuning for C500k
#22So, moving a /var/log (not just /var) on separate device connected to distinct controller port is a big deal.
If you're running, say, mail server, you should separate /var/spool and /var/log and /var/db/mysql if any.
Partitioning, serious network card (think Broadcom) and big CPU caches are good things to begin with.
Re: Linux Kernel Tuning for C500k
#23Re: Linux Kernel Tuning for C500k
#24Re: Linux Kernel Tuning for C500k
#25btw, the most common source of high load is (surprise!) disk I/O. So, moving a /var/log (not just /var) on separate device connected to distinct controller port is a big deal. If you're running, say, mail server, you should separate /var/spool and /var/log and /var/db/mysql if any. Partitioning, serious network card (think Broadcom) and big CPU caches are good things to begin with.
Re: Linux Kernel Tuning for C500k
#26http://news.ycombinator.com/item?id=1755575
Is maximum number of connections that you can reach on largest EC2 instance is the same as on physical server?