mirror of
https://git.haproxy.org/git/haproxy.git/
synced 2025-09-21 13:51:26 +02:00
b56a7c89a8
On process startup, the CPU topology of the machine is inspected. If a multi-socket CPU machine is detected, automatically define the process affinity on the first node with active cpus. This is done to prevent an impact on the overall performance of the process in case the topology of the machine is unknown to the user. This step is not executed in the following condition : - a non-null nbthread statement is present - a restrictive 'cpu-map' statement is present - the process affinity is already restricted, for example via a taskset call For the record, benchmarks were executed on a machine with 2 CPUs Intel(R) Xeon(R) CPU E5-2680 v3 @ 2.50GHz. In both clear and ssl scenario, the performance were sub-optimal without the automatic rebinding on a single node.
The HAProxy documentation has been split into a number of different files for ease of use. Please refer to the following files depending on what you're looking for : - INSTALL for instructions on how to build and install HAProxy - BRANCHES to understand the project's life cycle and what version to use - LICENSE for the project's license - CONTRIBUTING for the process to follow to submit contributions The more detailed documentation is located into the doc/ directory : - doc/intro.txt for a quick introduction on HAProxy - doc/configuration.txt for the configuration's reference manual - doc/lua.txt for the Lua's reference manual - doc/SPOE.txt for how to use the SPOE engine - doc/network-namespaces.txt for how to use network namespaces under Linux - doc/management.txt for the management guide - doc/regression-testing.txt for how to use the regression testing suite - doc/peers.txt for the peers protocol reference - doc/coding-style.txt for how to adopt HAProxy's coding style - doc/internals for developer-specific documentation (not all up to date)