5df0df96dd
This new command, enabled only with "DEBUG_DEV", sends 2 or 20 traces per task wakeup (depending on the verbosity level), and stops after 1M wakeups per thread in order not to have to stop/start the process each time it's fired. We have two small messages and 18 larger ones from 20 to 270 bytes each, so that the average size is approx 213 bytes counting headers (the header adds approx 82 bytes), which matches what's generally observed on average when traces are enabled in all muxes. Typical figures show varations between 5.7M and 6.2M msg/s on an EPYC in a 3C6T setup (single CCX), and 2.12M - 2.22M in a 24C48T setup (across 8 CCX, with 8 thread groups).
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)