mirror of
https://git.haproxy.org/git/haproxy.git/
synced 2025-11-26 21:31:01 +01:00
a64c703374
There are some situations, after sending a request or response, upon I/O completion, or applet execution, where we end up with an empty buffer that was not released. This results in excessive memory usage (back to 1.5) and a lower CPU cache efficiency since buffers are not recycled as fast. This has changed since the places where we send have changed with the new layering, but not all cases susceptible of leaving an empty buffer were properly spotted. Doing so reduces the memory pressure on buffers by about 2/3 in high traffic tests. This should be backported to 2.0 and maybe 1.9.
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)