fasthttp - maximum pool size

Hi,

 

 

Those properties of the FastHTTP profile refer to the OneConnect settings for the profile. So my interpretation of the max pool size count is that it indicates how many idle serverside TCP connections LTM will maintain at any given time. This is based on the details in SOL7208:

 

 

 

SOL7208: Overview of the OneConnect profile

 

https://support.f5.com/kb/en-us/solutions/public/7000/200/sol7208.html

 

 

OneConnect Profile Settings

 

...

 

The Maximum Size setting represents the maximum number of idle server-side connections kept in the connection pool.

 

The Maximum Age setting represents the maximum number of seconds a server-side connection is allowed before the connection is deleted from the connection pool.

 

 

 

 

I imagine that LTM would open more than 2048 server side connections if that were necessary to handle the client side requests. I don't think LTM would queue or close the clientside requests and keep only 2048 connections open between itself and the pool members if the serverside connection pool was "full". Maybe someone here can correct or confirm these assumptions.

 

 

You could also test this by setting the limit to 1 or 2 and making a few requests to the VIP with a tcpdump running.

 

 

If you'd like confirmation from F5 and/or for them to update the LTM config guide to make this more clear, you could open a case with F5 Support.

 

 

Aaron