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 2016/04/26 07:48:37 UTC
[27/38] logging-log4j2 git commit: LOG4J2-1297 small syntax edits
LOG4J2-1297 small syntax edits
Project: http://git-wip-us.apache.org/repos/asf/logging-log4j2/repo
Commit: http://git-wip-us.apache.org/repos/asf/logging-log4j2/commit/26d87c37
Tree: http://git-wip-us.apache.org/repos/asf/logging-log4j2/tree/26d87c37
Diff: http://git-wip-us.apache.org/repos/asf/logging-log4j2/diff/26d87c37
Branch: refs/heads/master
Commit: 26d87c37236ff200d57e18d5bebb41491fa945c8
Parents: 7730ae5
Author: rpopma <rp...@apache.org>
Authored: Mon Apr 25 23:49:21 2016 +0900
Committer: Ralph Goers <rg...@nextiva.com>
Committed: Mon Apr 25 21:30:30 2016 -0700
----------------------------------------------------------------------
src/site/xdoc/manual/garbagefree.xml | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/logging-log4j2/blob/26d87c37/src/site/xdoc/manual/garbagefree.xml
----------------------------------------------------------------------
diff --git a/src/site/xdoc/manual/garbagefree.xml b/src/site/xdoc/manual/garbagefree.xml
index c9e8692..6222a45 100644
--- a/src/site/xdoc/manual/garbagefree.xml
+++ b/src/site/xdoc/manual/garbagefree.xml
@@ -359,8 +359,8 @@ public void garbageFree() {
<a name="Throughput" />
<h4>Throughput of Garbage-free Logging May Be Worse (But It's All Relative)</h4>
- <p>Log4j 2.6 in garbage-free mode has the highest throughput in single-threaded scenarios. In multi-threaded
- scenarios, Log4j 2.6 "classic" has highest throughput, with Log4j 2.6 in garbage-free mode and Log4j 2.5
+ <p>In our measurements, Log4j 2.6 in garbage-free mode had the highest throughput in single-threaded scenarios. In multi-threaded
+ scenarios, Log4j 2.6 "classic" had the highest throughput, with Log4j 2.6 in garbage-free mode and Log4j 2.5
not far behind. Our test results suggest that the throughput of all other logging frameworks rapidly
declines in multi-threaded applications.</p>
<p>The graph below compares Log4j 2.6 in garbage-free mode to Log4j 2.6 "classic" mode (which allocates
@@ -369,7 +369,7 @@ public void garbageFree() {
Log4j 1.2.17, Logback and JUL use their respective File appenders. ImmediateFlush was set to <tt>false</tt> for all
loggers that support this. The JUL results are for the <tt>XMLFormatter</tt> (which in our measurements was
about twice as fast as the <tt>SimpleFormatter</tt>).</p>
- <p>The synchronous logging throughput results below are generated with the
+ <p>The synchronous logging throughput results below are obtained with the
<a href="http://openjdk.java.net/projects/code-tools/jmh/">JMH</a> Java benchmark harness.
See the <tt>org.apache.logging.log4j.perf.jmh.FileAppenderBenchmark</tt> source code in the log4j-perf module.</p>
<p><img src="../images/garbage-free2.6-SyncThroughputLinux.png"