|
|
Why not on by default?
Wow. it is a lot faster. Why isn't it on by default? Is there some problem caused by it which might make them choose not to turn it on? I couldn't see anything in the FAQ...
Why not on by default?
If in fact this does turn on HTTP KeepAlive, this would drastically increase the number of active threads handled by the web server at a given point, this is one reason for not using this as a default setting. This increases the workload handled by the server as the client sessions are changed from a stateless connection to a persistent connection, requiring the server to keep open threads instead of re-using them. In a nutshell, it reduces connection time as a session can re-use the same thread instead of opening a new one, but it causes a larger performance hit to web servers handling the sessions.
KeepAlive different from Pipelining
No, KeepAlive is what you actually meant. KeepAlive is an option (can be turned off both on the browser side and on the server side) in which the client and server can reuse the open connection. This does have somewhat impact on the server, since the connection (and hence thread/process) remains open (in case the client did not close it correctly) for a certain amount of time before it times out. My webserver had about 10% processing hit when ALL clients were using KeepAlive. That's not that much, considering you do less process forking and handle all requests much faster.
|
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments last 2 daysLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.13 seconds |
|