mirror of
https://github.com/haproxy/haproxy.git
synced 2026-04-15 21:59:41 -04:00
HAProxy - Load balancer
The NUMA detection code tries not to interfer with any taskset the user could have specified in init scripts. For this it compares the number of CPUs available with the number the process is bound to. However, the CPU count is retrieved after being applied an upper bound of MAX_THREADS, so if the machine has more than 64 CPUs, the comparison always fails and makes haproxy think the user has already enforced a binding, and it does not pin it anymore to a single NUMA node. This can be verified by issuing: $ socat /path/to/sock - <<< "show info" | grep thread On a dual 48-CPU machine it reports 64, implying that threads are allowed to run on the second socket: Nbthread: 64 With this fix, the function properly reports 96, and the output shows 48, indicating that a single NUMA node was used: Nbthread: 48 Of course nothing is changed when "no numa-cpu-mapping" is specified: Nbthread: 64 This can be backported to 2.4. |
||
|---|---|---|
| .github | ||
| addons | ||
| admin | ||
| dev | ||
| doc | ||
| examples | ||
| include | ||
| reg-tests | ||
| scripts | ||
| src | ||
| tests | ||
| .cirrus.yml | ||
| .gitattributes | ||
| .gitignore | ||
| .mailmap | ||
| .travis.yml | ||
| BRANCHES | ||
| CHANGELOG | ||
| CONTRIBUTING | ||
| INSTALL | ||
| LICENSE | ||
| MAINTAINERS | ||
| Makefile | ||
| README | ||
| SUBVERS | ||
| VERDATE | ||
| VERSION | ||
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)