On 25/11/2014 18:08, Lukas Tribus wrote:
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
Ok that's strange then because we don't have a very complex config. About 8 front-ends of which only 3 are busy. About 10 back-end pools each containing 30-60 servers. Things start getting hot when we're serving about 15,000 requests per second (about 1Gb/s bandwidth).
Is there any way we can find out why we're using so much cpu? We used perf to create a flame graph which is here: http://www.cjx.com/perf-kernel.svg - taken when the system was not very loaded - perhaps somebody with better
knowledge of haproxy than I can tell if something is awry...
