Geek asks and answers

Keep-Alive HTTP for calls <1K every 1 second

I am optimizing my web server settings to handle a large number of concurrent users, and one of the problems I encounter is the decision to disable HTTP Keep-Alive.

I use CDN for all the images on the site, so when my HTML page is requested, I upload about 5 files (js, css, etc.) on the first load ... and then only HTML for each subsequent download.

Another, then the only thing I have is an HTTP POST update invoke for every second (as a result, JSON is usually less than 1 KB).

So, with these limitations - do you think disabling HTTP Keep-Alive on the server would be a good idea? Could this improve the number of concurrent user servers?

(By the way, I reduced KeepAliveTimeout / ConnectionTimeout to 15 seconds in IIS 7.5 settings)

+3
source share
1 answer

, , . , , . , 100 . , Http Keep-Alive 15 15 , ( ) 1,5 - , / ( , - ). , , , 8-9 .

, , . , .. - / . , keep-alive, .

, . SO: http keep-alive

+1

More articles:


All Articles