So in this case NGINX is terminating SSL, and the upstream is HAPROXY
running the same server. HAProxy applies routing rules and distributes
requests to a pool of ~500 servers in round robin fashion. In this case
we're most interested in keeping the connections between NGINX to HAPROXY
alive. The N
Hello!
On Thu, Nov 05, 2015 at 12:55:36AM -0500, CJ Ess wrote:
> So I'm looking for some advice on determining an appropriate number for the
> keepalive parameter within an upstream stanza.
>
> They server processes ~3000 requests per second, and haproxy is the single
> upstream destination. Div
So I'm looking for some advice on determining an appropriate number for the
keepalive parameter within an upstream stanza.
They server processes ~3000 requests per second, and haproxy is the single
upstream destination. Dividing by the request rate by the number of
processors (workers) I'm thinkin
