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/07 15:01:34 UTC
logging-log4j2 git commit: LOG4J2-1179 various small fixes
Repository: logging-log4j2
Updated Branches:
refs/heads/master d4866b0c2 -> 2cd922b61
LOG4J2-1179 various small fixes
Project: http://git-wip-us.apache.org/repos/asf/logging-log4j2/repo
Commit: http://git-wip-us.apache.org/repos/asf/logging-log4j2/commit/2cd922b6
Tree: http://git-wip-us.apache.org/repos/asf/logging-log4j2/tree/2cd922b6
Diff: http://git-wip-us.apache.org/repos/asf/logging-log4j2/diff/2cd922b6
Branch: refs/heads/master
Commit: 2cd922b618e28b428ef779de3b514f4e4e0f48f6
Parents: d4866b0
Author: rpopma <rp...@apache.org>
Authored: Sun May 8 00:01:58 2016 +0900
Committer: rpopma <rp...@apache.org>
Committed: Sun May 8 00:01:58 2016 +0900
----------------------------------------------------------------------
src/site/xdoc/performance.xml | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/logging-log4j2/blob/2cd922b6/src/site/xdoc/performance.xml
----------------------------------------------------------------------
diff --git a/src/site/xdoc/performance.xml b/src/site/xdoc/performance.xml
index 309e946..26a8f7a 100644
--- a/src/site/xdoc/performance.xml
+++ b/src/site/xdoc/performance.xml
@@ -166,9 +166,6 @@ if (logger.isDebugEnabled()) {
The graph below compares the throughput of logging messages with parameters using various logging libraries.
These are all asynchronous logging calls, so these numbers do not include the cost of disk I/O
and represent <em>peak</em> throughput.</p>
- <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>JUL (java.util.logging) does not have a built-in asynchronous Handler.
<a href="https://docs.oracle.com/javase/8/docs/api/java/util/logging/MemoryHandler.html">MemoryHandler</a>
is the nearest thing available so we included it here.
@@ -176,6 +173,9 @@ if (logger.isDebugEnabled()) {
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.
However, when more application threads are logging concurrently, the cost of lock contention outweighs this gain.</p>
+ <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><img src="images/ParamMsgThrpt1-4T.png" /></p>
<p>The results above are for JUL (java.util.logging) 1.8.0_45, Log4j 2.6, Log4j 1.2.17 and Logback 1.1.7,
and were obtained with the
@@ -185,7 +185,7 @@ if (logger.isDebugEnabled()) {
</p>
<a name="asyncLoggingWithLocation" />
- <h4>Performance Impact of Capturing Location Information on Asynchronous Logging Throughput</h4>
+ <h4>Asynchronous Logging with Caller Location Information</h4>
<p>
Some layouts can show the class, method and line number in the application where the logging call was made.
In Log4j 2, examples of such layout options are HTML