You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@logging.apache.org by rg...@apache.org on 2012/09/22 17:38:46 UTC
svn commit: r1388822 - in /logging/log4j/log4j2/trunk:
core/src/test/resources/logback-perf.xml src/site/xdoc/performance.xml
Author: rgoers
Date: Sat Sep 22 15:38:46 2012
New Revision: 1388822
URL: http://svn.apache.org/viewvc?rev=1388822&view=rev
Log:
Update performance page to correct inaccurate information
Modified:
logging/log4j/log4j2/trunk/core/src/test/resources/logback-perf.xml
logging/log4j/log4j2/trunk/src/site/xdoc/performance.xml
Modified: logging/log4j/log4j2/trunk/core/src/test/resources/logback-perf.xml
URL: http://svn.apache.org/viewvc/logging/log4j/log4j2/trunk/core/src/test/resources/logback-perf.xml?rev=1388822&r1=1388821&r2=1388822&view=diff
==============================================================================
--- logging/log4j/log4j2/trunk/core/src/test/resources/logback-perf.xml (original)
+++ logging/log4j/log4j2/trunk/core/src/test/resources/logback-perf.xml Sat Sep 22 15:38:46 2012
@@ -19,6 +19,7 @@
<appender name="TestLogfile" class="ch.qos.logback.core.FileAppender">
<file>target/testlogback.log</file>
<encoder>
+ <immediateFlush>false</immediateFlush>
<Pattern>%d{ISO8601} %5p [%t] %c{0} %X{transactionId} - %m%n</Pattern>
</encoder>
</appender>
Modified: logging/log4j/log4j2/trunk/src/site/xdoc/performance.xml
URL: http://svn.apache.org/viewvc/logging/log4j/log4j2/trunk/src/site/xdoc/performance.xml?rev=1388822&r1=1388821&r2=1388822&view=diff
==============================================================================
--- logging/log4j/log4j2/trunk/src/site/xdoc/performance.xml (original)
+++ logging/log4j/log4j2/trunk/src/site/xdoc/performance.xml Sat Sep 22 15:38:46 2012
@@ -112,7 +112,7 @@
<b>The performance of deciding whether to log or not to log when logging is turned on.</b>
<br/>
<p>
- Unlike Log4j and Logback, Log4j 2 Loggers don't "walk a hierarchy". Loggers point directly to the
+ Unlike Log4j, Log4j 2 Loggers don't "walk a hierarchy". Loggers point directly to the
Logger configuration that best matches the Logger's name. This incurs extra overhead when the Logger
is first created but reduces the overhead every time the Logger is used.
</p>
@@ -127,9 +127,9 @@
delivering log events will never be insignificant. For example, the results of writing to a simple log
file using the same format using Log4j, Logback and Log4j 2 are:
<pre>
- Log4j: 4220
- Logback: 9671
- Log4j 2: 4615
+ Log4j: 1427
+ Logback: 1401
+ Log4j 2.0: 1963
</pre>
</p>
<p>