Hi, On Fri, Feb 15, 2013 at 04:21:28PM -0500, Chris Burroughs wrote: > http://comments.gmane.org/gmane.comp.web.haproxy/8307 > > So my understanding is that is is generally not helpful to increase > nbproc and instead pinning NIC IRQs and haproxy on two adjacent cores is > recommended for handling a high connection rate. In the case of using > multiple NICs, more NIC/haproxy pairs can be pinned. > > How does this recommendation change when two NICs are available and > tproxy is being used? Should the backend requests all use one NIC, and > outgoing client the other? If there are no bandwidth requirements to > use both NICs, should one one be used to reduce interrupts?
My observations have been that using the same NIC for in+out is best whenever possible. But I also know that you don't always have the choice. If you have to use one NIC per side, observations show that Tx costs a lot less than Rx and that the NIC with the most Rx traffic (generally the one facing the server) should have its own CPU, and that you can mix haproxy with the NIC sending the traffic outside. But you can generally as well have the two NICs bound to the same CPU core and have haproxy run on the other core. Ideally you should experiment a bit. Hoping this helps, Willy
