3 ms·

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 wi

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#keepalive_timeout 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.

zamadatix 7y ago
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#keepalive_timeout 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.

zamadatix 7y ago

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#keepalive_timeout 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.