This is an automated email from the ASF dual-hosted git repository.
swebb2066 pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/logging-log4cxx.git
The following commit(s) were added to refs/heads/master by this push:
new 923d9c10 Advertise Log4cxx 1.6 benefits in web-site documentation
(#553)
923d9c10 is described below
commit 923d9c10aea7b4749d8603c42ab473f00f3668b4
Author: Stephen Webb <[email protected]>
AuthorDate: Sun Oct 12 12:12:01 2025 +1100
Advertise Log4cxx 1.6 benefits in web-site documentation (#553)
---
src/site/markdown/configuration-samples.md | 2 +-
src/site/markdown/performance.md | 12 ++++++++++++
2 files changed, 13 insertions(+), 1 deletion(-)
diff --git a/src/site/markdown/configuration-samples.md
b/src/site/markdown/configuration-samples.md
index 6a83e15d..30cbbaca 100644
--- a/src/site/markdown/configuration-samples.md
+++ b/src/site/markdown/configuration-samples.md
@@ -86,7 +86,7 @@ The variable names are [documented here](@ref
log4cxx.spi.Configurator.propertie
To check the correct values are used when your configuration file is loaded,
use [Log4cxx internal debugging].
-# Configuring a logger to use asynchronous output
+# Configuring a logger to use asynchronous output {#asynch-output}
Log4cxx 1.6 allows you to more easily attach an [AsyncAppender](@ref
log4cxx.AsyncAppender)
to a logger using a configuration file.
diff --git a/src/site/markdown/performance.md b/src/site/markdown/performance.md
index 608e5cc7..3f033719 100644
--- a/src/site/markdown/performance.md
+++ b/src/site/markdown/performance.md
@@ -25,6 +25,17 @@ 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 output 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
+of your application's thread 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
@@ -142,3 +153,4 @@ When logging floating point values from a high priority
thread,
and you cannot use a background thread to format and write the log data,
the LOG4CXX_[level]_FMT series of macros impose the least overhead.
+[asynchronous output setting]:configuration-files.html#asynch-output
