Hi,
Currently, HAproxy support connection re-use which may improve performance
when the client (front-end) use pool of connections. but , some times the
client close the connection immediately after getting the server response.
so, connection reuse will not give benefit.
Unfortunately , in my case the client use HTTP and doesn't keep the
connections open after getting the response.
The server use HTTPS 2 way SSL.
HAproxy "need" to open and close a lot of connections to the server/s
include the 2 way SSL which is CPU intensive.
In this case using connection reuse will not help to reduce opening
connections to the servers.
Would you consider adding the ability of maintaining an
independent connection pool towards the back-end servers regardless of the
front-end clients connections in HAProxy next release?
thanks
Amir Yosef
Currently, HAproxy support connection re-use which may improve performance
when the client (front-end) use pool of connections. but , some times the
client close the connection immediately after getting the server response.
so, connection reuse will not give benefit.
Unfortunately , in my case the client use HTTP and doesn't keep the
connections open after getting the response.
The server use HTTPS 2 way SSL.
HAproxy "need" to open and close a lot of connections to the server/s
include the 2 way SSL which is CPU intensive.
In this case using connection reuse will not help to reduce opening
connections to the servers.
Would you consider adding the ability of maintaining an
independent connection pool towards the back-end servers regardless of the
front-end clients connections in HAProxy next release?
thanks
Amir Yosef