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/04/25 16:49:08 UTC

logging-log4j2 git commit: LOG4J2-1297 small syntax edits

Repository: logging-log4j2
Updated Branches:
  refs/heads/master 62891aff4 -> 1c3c5257e


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/1c3c5257
Tree: http://git-wip-us.apache.org/repos/asf/logging-log4j2/tree/1c3c5257
Diff: http://git-wip-us.apache.org/repos/asf/logging-log4j2/diff/1c3c5257

Branch: refs/heads/master
Commit: 1c3c5257eff4cc7ea6a56b213c2bea04a8e63cbe
Parents: 62891af
Author: rpopma <rp...@apache.org>
Authored: Mon Apr 25 23:49:21 2016 +0900
Committer: rpopma <rp...@apache.org>
Committed: Mon Apr 25 23:49:21 2016 +0900

----------------------------------------------------------------------
 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/1c3c5257/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"