dc5f81140f
When task profiling is enabled, the reported CPU time for short requests and responses (e.g. redirect) is always zero in the logs, because process_stream() is only called once and the CPU time is measured after it returns. This is particuarly annoying when dealing with denies and in general anything that deals with parasitic traffic because it can be difficult to figure where the CPU is spent. The solution taken in this patch consists in having process_stream() update the cpu time itself before logging and quitting. It's very simple. It will not take into account the time taken to produce the log nor freeing the stream, but that's marginal compared to always logging zero. The task's wake_date is also reset so that the scheduler doesn't have to perform these operations again. This is dependent on the following patch: MINOR: sched: store the current profile entry in the thread context It should be backported to 2.6 as it does help for troubleshooting. (cherry picked from commit beee600491c15861a923113ee322c9f57aba07e5) Signed-off-by: Christopher Faulet <cfaulet@haproxy.com>
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)