This is an automated email from the ASF dual-hosted git repository. swebb2066 pushed a commit to branch update_performance_web_info in repository https://gitbox.apache.org/repos/asf/logging-log4cxx.git
commit c7fad19d30f4c84a2f328fa843dfecd8f1ba2faf Author: Stephen Webb <[email protected]> AuthorDate: Sat Oct 11 15:22:46 2025 +1100 Advertise Log4cxx 1.6 benefits in web-site documentation --- src/site/markdown/performance.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/src/site/markdown/performance.md b/src/site/markdown/performance.md index 608e5cc7..653ce180 100644 --- a/src/site/markdown/performance.md +++ b/src/site/markdown/performance.md @@ -25,6 +25,16 @@ One important question with a logging library is: is it fast enough? While Log4cxx may not be the fastest logging implementation, it is more than fast enough for the vast majority of cases. +Using Log4cxx 1.6 you can even use microsecond timestamps +in TRACE level logging messages to quickly get a sense of +where your application's workload is concentrated. +The LOG4CXX_XXXX_ASYNC macros in Log4cxx 1.6 +just capture values in a buffer +and by adding the new "asynchronous=true" setting to your configuration file, +the values are converted to text in a background thread. +That combination prevents TRACE level logging being the dominate CPU load and +provides the lowest overhead logging in the history of Log4cxx. + While Log4cxx can generate 2,000,000 log messages/second, skipping a disabled logging request requires only a few nano-seconds, so application performance is not affected when
