Comment by zamadatix
7 years ago
> Also, wtf are you talking about?
TTLS.
> Did you even read the article?
Sure did which is why I referenced it.
> Most sit between? 0-15 minutes.
This is true in that the range encapsulates most keep-alive timeouts not in that keepalives longer than a minute or two are actually the majority. nginx defaults to 100 seconds, Apache is less than that. Most don't mess with these let alone bump them to 900. Generally 60 to 120 is considered standard with some cap on the number of active keep-alive sessions as well. Some go ultra-low or disable it all together, very few go ultra-high.
> WTF is your timeout?
120.
Also please try to keep the conversations together.
TTLS isn't a thing.
You're argument about keep alive makes no sense. You're confusing the nginx documentation. 100 is the number of default connections it will hold open. 60 is the default timeout. Also it's sent as an HTTP response to the client in the headers...
Here you need to read up: https://nginx.org/en/docs/http/ngx_http_core_module.html#kee...
The timeout only matters if you're not making requests. Setting a low keep alive will actually result in more DNS requests...doh
Next you're going to tell me you only write blocking code and use a thread per connection...
I guess you haven't created many 10k concurrent app servers.
Meant "TTLs" as in the plural of TTL but my phone capitalized the whole block on me.
> You're argument about keep alive makes no sense. You're confusing the nginx documentation. 100 is the number of default connections it will hold open. 60 is the default timeout. Also it's sent as an HTTP response to the client in the headers... Here you need to read up: http://nginx.org/en/docs/http/ngx_http_core_module.html#keep...
Are you're right about the 100 being the default active keepalives not the default timeout. According to your own nginx link 75 is the timeout not 60 though: "Default: keepalive_timeout 75s;"
Either way, 75/60/100/120 are significantly far off from 15 minutes.
> The timeout only matters if you're not making requests.
Or if the server reaches max connections.
> Setting a low keep alive will actually result in more DNS requests...doh
Which is how the discussion on DNS TTLs comes about in the first place. It's trivial to set the DNS TTL astronomically higher than the HTTP keep-alive, in which case the browser & OS won't actually make a lookup request since it's cached.