4 ms·
Apache's thread-per-connection model used to run basically the entire internet until nginx came along and demonstrated 10k simultaneous connections on a single
by wongarsu 5y ago
Apache's thread-per-connection model used to run basically the entire internet until nginx came along and demonstrated 10k simultaneous connections on a single server.
If you only have around 100 concurrent confections, a separate thread per connection is entirely feasible. A whole new process is probably fine on Linux, but e.g. Windows takes pretty long to spawn a process
- einpoklum 5y agoIf you have 100 concurrent confections you're probably baking cookies.
- wongarsu 5y agoBut you can probably get away with using one regular commercial oven instead of getting a baking tunnel oven :)
- TZubiri 5y agoTo be fair, I think it would be ideal if every service would run their own 100 concurrent connections, instead of everyone using a service that handles 1 trillion.
- minusf 5y agothe default mode in apache/apache2 used to be _process_ per connection (pre forked workers) not thread per connection. threads came much later.
- jiofih 5y agoYou might want to review that knowledge. You can spawn a few thousand threads on a modern machine without much contention.
- merb 5y agowell the thing is he confuses processes with threads. apache2-prefork used/uses processes and not threads.