3 ms·
There's no way the connection just sits idle and the worker can't serve other requests for the full timeout, right? That just sounds... Wrong. And is not consis
by weird-eye-issue 4y ago
There's no way the connection just sits idle and the worker can't serve other requests for the full timeout, right? That just sounds... Wrong. And is not consistent with load testing I've done before with a nginx setup
- dijonman2 4y agoApache will spawn a process (at least with pfork) and the process will wait for a keep alive connection to send a new req. Everything old is new again. Gotta tune it out.
- weird-eye-issue 4y agoIs this true? So Apache basically launches a Slowloris attack on itself for every connection?
- dijonman2 4y agoWith prefork there is one process per connection. Look at server-status. There was a threaded version as of 2.4 but I don’t think it worked well.
- danuker 4y agoDepends on the concurrency ability of the web server (async) or parallelism (threads)