Greetings. Could someone help me understand LTM pool Connections vs. Requests here? Why would Requests be so much higher than Connections and, even more, so much higher between nodes? The pool is Round Robin.
By default, the BIG-IP system performs load balancing once for each TCP connection, rather than for each HTTP request within that connection. After the initial TCP connection is load balanced, all HTTP requests seen on the same connection are sent to the same pool member. You can modify this behavior by forcing the server-side connection to detach after each HTTP request, which in turn allows a new load balancing decision according to changing persistence information in the HTTP request.
You can force the server-side detachment by either applying both an HTTP profile and a OneConnect profile to the virtual server, or by using an iRule to explicitly detach the server-side connection before each HTTP response request.
By default, the BIG-IP system performs load balancing once for each TCP connection, rather than for each HTTP request within that connection. After the initial TCP connection is load balanced, all HTTP requests seen on the same connection are sent to the same pool member. You can modify this behavior by forcing the server-side connection to detach after each HTTP request, which in turn allows a new load balancing decision according to changing persistence information in the HTTP request.
You can force the server-side detachment by either applying both an HTTP profile and a OneConnect profile to the virtual server, or by using an iRule to explicitly detach the server-side connection before each HTTP response request.
