Zuul Connection Pool properties

[mehmetgul]

Hi Team,
I was testing and trying to understand the behaviour of zuul properties but I need more info specifically on perServerWaterline.
I check the documentations and googled a lot but didn't get enough info.
Ribbon Client Config Property <originName>.ribbon.MaxConnectionsPerHost <origin>.concurrency.max.requests <originName>.netty.client.perServerWaterline //default value=4

I got clarifications on MaxConnectionsPerHost and max.requests but when I tested the perServerWaterline didn't understand its behaviour.
I was testing the connection limits and I set the perServerWaterline=1 and run performance test for 20K req/min and 40K req/min with 1 sec, 2sec and 4sec delay. Total 5 test. (Attaching the brief test result)
I know that this property is for per server, per event loop and per event is for 1 CPU.
So we are having 2 container and each container having 2CPU.
Base on my test results the error rates are very less despite of setting the limit 1.
Do we suppose to set another property along with this or this property is meant to handle in different way?
I having difficulty to understand the purpose of this property.
Can someone provide more details on this property.
Thanks
[

]

[jguerra]

perServerWaterline controls how many idle connections a single event loop can have to a particular server in its connection pool. Setting perServerWaterline=1 essentially disables connection pooling since the connection will be closed when it is returned to the pool, see PerServerConnectionPool.release().

[github-actions]

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days.