mirror of
https://git.haproxy.org/git/haproxy.git/
synced 2025-09-21 05:41:26 +02:00
75cc65356f
resolv_hostname_cmp() is bogus, it is applied on labels and not plain names, but doesn't make any distinction between length prefixes and characters, so it compares the labels lengths via tolower() as well. The only reason for which it doesn't break is because labels cannot be larger than 63 bytes, and that none of the common encoding systems have upper case letters in the lower 63 bytes, that could be turned into a different value via tolower(). Now that all labels are stored in lower case, we don't need to burn CPU cycles in tolower() at run time and can use memcmp() instead of resolv_hostname_cmp(). This results in a ~22% lower CPU usage on large farms using SRV records: before: 18.33% haproxy [.] resolv_validate_dns_response 10.58% haproxy [.] process_resolvers 10.28% haproxy [.] resolv_hostname_cmp 7.50% libc-2.30.so [.] tolower 46.69% total after: 24.73% haproxy [.] resolv_validate_dns_response 7.78% libc-2.30.so [.] __memcmp_avx2_movbe 3.65% haproxy [.] process_resolvers 36.16% total
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)