Differences

This shows you the differences between two versions of the page.

--- litespeed_wiki:config:keep_alive [2016/09/15 21:39]
Jackson Zhang created
+++ litespeed_wiki:config:keep_alive [2016/09/16 19:14]
Rob Holda
@@ Line 1: / Line 1: @@
 ====== Understanding "keep alive" settings ======
-LSWS turn on "keep alive" setting by default. It is server level configuration and can not be controlled/overridden at virtual host level.  There is no "yes/no" "on/off" option under LSWS Admin Console-> Server -> Tuning -> Connection section. However, you can control it through "Max Keep-Alive Requests" "Smart Keep-Alive" "Keep-Alive Timeout (secs)" settings. Please bear in mind that you don't need to enable "Smart Keep-Alive" to be able to use "Keep-Alive". Actually,  "Smart Keep-Alive" is designed to exclude some types of files from "Keep-Alive" connections. For example, set keep-alive connections for requests of JavaScript, CSS Style Sheet, image files only, excluding other type of files. With latest release of 5.1.8, it only excludes HTML from keep alive. If you would like to make everything, turn off "Smart Keep-Alive".
+LiteSpeed Web Server turns on "keep alive" by default. There is no "yes/no" or "on/off" option in LSWS configuration, however, you can turn it off or control it through the "Max Keep-Alive Requests", "Smart Keep-Alive", and "Keep-Alive Timeout (secs)" settings (under the LSWS Admin Console -> Server -> Tuning -> Connection section).
-How to control "Keep A-alive"?
+{{ :litespeed_wiki:config:keep-alive.png?nolink&300 |}}
-Set "Max Keep-Alive Requests" to "0" or "1" will disable "keep-alive". Leave as default if you have no special requirement. Adjust it to a little higher when you would like to fine tune your server. Or even adjust it to BIG value, like "100,000", when you do a benchmark test.
+Please bear in mind that you don't need to enable "Smart Keep-Alive" to be able to use "Keep-Alive". Actually, "Smart Keep-Alive" is designed to "turn off" Keep-Alive for some types of files, instead of "turning it on". For example, it will "enable" keep-alive for JavaScript, CSS, image file requests, and disable it for other type of files, such as HTML files. Since release 5.1.8, it will only exclude HTML from keep-alive. If you would like to use keep-alive for everything, you must turn off "Smart Keep-Alive".
-Default Keep-Alive Timeout (secs) is "5". You don't need to adjust it unless you have special requirement.
-Sometimes you may be wondering why you did not see Keep-alive header for a particular URL. Is the "keep-alive" on? Yes, it is on by default. Don't try to turn on "Smart Keep-Alive" since it is actually to turn off some files. So turn off " "Smart Keep-Alive".  "Max Keep-Alive Requests" setting may be increased. Also PHP external app "Soft Limit" may also limit "keep-alive" connections.
+"Keep-alive" is server level configuration and can not be controlled at virtual host level.
+==== Controlling "Keep-Alive" ====
+Setting "Max Keep-Alive Requests" to "0" will disable "keep-alive". You should leave this as the default value if you have no special requirements, increasing it slightly as needed or even adjusting it to a large value, like "100,000", when you do a benchmark test.
+The default value for Keep-Alive Timeout (secs) is "5". You don't need to adjust this either unless you have some special requirements.
+Sometimes you may not see a Keep-alive header for a particular URL. This does not mean that "keep-alive" is off. To troubleshoot this you may turn off "Smart Keep-Alive" and increase the value of the "Max Keep-Alive Requests" setting. Sometimes a PHP external application "Soft Limit" may also limit "keep-alive" connections. Increasing this "Soft Limit" may also fix this issue.