On Mon, Oct 27, 2014 at 7:41 PM, Chris Allen <ch...@cjx.com> wrote: > We're running haproxy on a 2x4 core Intel E5-2609 box. At present haproxy is > running on > a single core and saturating that core at about 15,000 requests per second. > > Our application has four distinct front-ends (listening on four separate > ports) so it would be > very easy for us to run four haproxy instances, each handling one of the > four front-ends. > > This should then allow us to use four of our eight cores. However we won't > be able to tie hardware > interrupts to any particular core. > > Is this arrangement likely to give us a significant performance boost? Or > are we heading for trouble because > we can't tie interrupts to any particular core? > > Any advice would be much appreciated. Many thanks, > > Chris. > >
Hi Chris, You can use nbproc, cpu-map and bind-process keywords to startup multiple processes and bind frontends and backends to multiple CPU cores. Haproxy
