> Hi, > > Thanks for your reply. We have tried this approach and while it gives > some benefit, the haproxy process itself > remains cpu-bound, with no idle time at all - with both pidstat and perf > reporting that it uses close to 100% > of available cpu while running.
I think SSL/TLS termination is the only use case where HAProxy saturates
a CPU core of a current generation 3,4Ghz+ CPU, which is why scaling
SSL/TLS is more complex, requiring nbproc> 1.
Lukas
