Your server is choking on C10k? Put your non-blocking sockets to work and optimize! Your product manager thinks you're an unscalable junior? Fire up the event loop! I want you to solve your problems by scaling to O(1)
C10K problem
in 1999 a software engineer named Dan Kegel wrote an article that changed how web servers are built
the question was simple how do you handle 10,000 concurrent connections on one machine
at the time Apache used one thread per connection, each thread needed memory for its stack around 8MB and 10,000 connections meant around 80GB of RAM just for stacks
the system spent more time switching threads than doing real work
servers crashed long before reaching 10k connections
this became known as the C10K problem