4 ms·
> A better model already exists - thread per connection - for the majority of what we want as web developers. Haven't we already seen in Apache vs Nginx that t
by lazyant 6y ago
> A better model already exists - thread per connection - for the majority of what we want as web developers.
Haven't we already seen in Apache vs Nginx that thread per connection will OOM the web servers under heavy traffic? (haven't used Apache in many years so this may be obsolete)
- drzaiusx11 6y agoApache moved from using a thread per connection to fibers years ago [1]. Fibers are simpler than green threads (cooperative multitasking via yielding) which should be illustrative of how good an idea the "thread per connection" model is. Although it could be argued that fibers are a type of primitive thread--so as long you don't mean OS thread the idea has merit. [1] http://httpd.apache.org/dev/whiteboard/process-model.html http://httpd.apache.org/dev/whiteboard/process-model.html