You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@logging.apache.org by rp...@apache.org on 2016/05/06 05:53:14 UTC
logging-log4j2 git commit: LOG4J2-1179 highlight the conclusion of
the parameterized message paragraph
Repository: logging-log4j2
Updated Branches:
refs/heads/master c8c21f0ee -> 8821a0ae5
LOG4J2-1179 highlight the conclusion of the parameterized message paragraph
Project: http://git-wip-us.apache.org/repos/asf/logging-log4j2/repo
Commit: http://git-wip-us.apache.org/repos/asf/logging-log4j2/commit/8821a0ae
Tree: http://git-wip-us.apache.org/repos/asf/logging-log4j2/tree/8821a0ae
Diff: http://git-wip-us.apache.org/repos/asf/logging-log4j2/diff/8821a0ae
Branch: refs/heads/master
Commit: 8821a0ae5c69ca60e0599c7635111d5ebe5ceb06
Parents: c8c21f0
Author: rpopma <rp...@apache.org>
Authored: Fri May 6 14:53:38 2016 +0900
Committer: rpopma <rp...@apache.org>
Committed: Fri May 6 14:53:38 2016 +0900
----------------------------------------------------------------------
src/site/xdoc/performance.xml | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/logging-log4j2/blob/8821a0ae/src/site/xdoc/performance.xml
----------------------------------------------------------------------
diff --git a/src/site/xdoc/performance.xml b/src/site/xdoc/performance.xml
index 5b44116..d1c31f3 100644
--- a/src/site/xdoc/performance.xml
+++ b/src/site/xdoc/performance.xml
@@ -156,9 +156,9 @@ if (logger.isDebugEnabled()) {
<em>before</em> passing off the log event to the background thread.</p>
<p>This is the safe thing to do, but the formatting has a performance cost.
The graph below compares the throughput of logging messages with parameters using various logging libraries.
- In absolute numbers, Log4j 2's Async Loggers perform well compared to the other logging
- frameworks, but notice that the cost increases with the number of parameters.
- In this area, Log4j 2 still has work to do to improve.</p>
+ In absolute numbers, <em>Log4j 2's Async Loggers perform well compared to the other logging
+ frameworks, but notice that the message formatting cost increases with the number of parameters.
+ In this area, Log4j 2 still has work to do to improve.</em></p>
<p>Note that the java.util.logging MemoryHandler does <em>not</em> do the safe thing of taking a snapshot
of the current parameter state (it just keeps a reference to the original parameter objects),
and as a result it is very fast when single-threaded.