3 ms·

Are you talking about HTTP keepalive or TCP keepalive? Keepalives can actually reduce the performance of a server with many concurrent clients (i.e. a benchmar

by mholt 4y ago

Are you talking about HTTP keepalive or TCP keepalive? Keepalives can actually reduce the performance of a server with many concurrent clients (i.e. a benchmark test), and have other weird effects on benchmarks: https://www.nginx.com/blog/http-keepalives-and-web-performance/ https://www.nginx.com/blog/http-keepalives-and-web-performan...

teknopaul 4y ago
Same thing. Http has no keep alive feature, you don't send http keep alive requests, if http 1.1 asks for keepalives it's a tcp thing.
- mholt 4y ago
  They are distinct in Go. The standard library uses "HTTP keep-alive" to mark connections as idle based on most recent HTTP request, whereas TCP keep-alive checks only ACKs.
- skyde 4y ago
  http 2.0 has keep alive!