5 ms·
Throw in a big keepalive and on a short test you can make it so it only processes 800 requests! Awesome. Lets try this with the worker mpm instead.
by ericb 15y ago
Throw in a big keepalive and on a short test you can make it so it only processes 800 requests! Awesome.
Lets try this with the worker mpm instead.
- peterwwillis 15y agoHell, let's get crazy and use event. I hear asynchronous connection handling is popular these days. http://httpd.apache.org/docs/2.4/mod/event.html http://httpd.apache.org/docs/2.4/mod/event.html
- sciurus 15y agoThe event MPM (new in Apache 2.4) is designed to address this: This MPM tries to fix the 'keep alive problem' in HTTP. After a client completes the first request, the client can keep the connection open, and send further requests using the same socket. This can save signifigant overhead in creating TCP connections. However, Apache HTTP Server traditionally keeps an entire child process/thread waiting for data from the client, which brings its own disadvantages. To solve this problem, this MPM uses a dedicated thread to handle both the Listening sockets, all sockets that are in a Keep Alive state, and sockets where the handler and protocol filters have done their work and the only remaining thing to do is send the data to the client. http://httpd.apache.org/docs/2.4/mod/event.html http://httpd.apache.org/docs/2.4/mod/event.html