OneConnect profile and OneConnectin fastHTTP

Hi,

 

When comparing OneConnect profile and OneConnect section of fasthttp profile it seems that implementation in fasthttp is more advanced. There are additional settings like:

 

• Minimum Pool Size
• Ramp-Up Increment
• Replenish

that are not in OneConnect profile. If I am not wrong those two settings are interconnected somehow. My understanding is that when Minimum is set to some value other that 0 then (with Replenish enabled) after number of connections drops below minimum new connections between LTM and backend servers are created by LTM (even without incoming client connections) in increments equal to Ramp-up. So for default value 4 new connections will be created as long as there is more connections than minimum. That is wild guess as I was not able to find good SOL describing this process.

 

If above is true I assume that difference between OneConnect profile and OC settings for fasthttp is in setting connections to the server. OC profile is not creating connections before receiving client connection and fasthttp is creating connections in advance (when minimum is set to something other than 0).

 

I wonder why OC profile is not using the same settings as OC in fasthttp? From technical point of view I can't see any reason why there is no option to create backend connections in advance for OC profile enabled VS - or there are some I am missing?

 

Piotr