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/09 17:38:05 UTC
logging-log4j2 git commit: LOG4J2-1297 improve description of
synchronous file logging response time graph
Repository: logging-log4j2
Updated Branches:
refs/heads/master 1e7f9f11c -> 51ff83ce7
LOG4J2-1297 improve description of synchronous file logging response time graph
Project: http://git-wip-us.apache.org/repos/asf/logging-log4j2/repo
Commit: http://git-wip-us.apache.org/repos/asf/logging-log4j2/commit/51ff83ce
Tree: http://git-wip-us.apache.org/repos/asf/logging-log4j2/tree/51ff83ce
Diff: http://git-wip-us.apache.org/repos/asf/logging-log4j2/diff/51ff83ce
Branch: refs/heads/master
Commit: 51ff83ce7fb2c2395efb5b2a668f0cc2a96aa1bb
Parents: 1e7f9f1
Author: rpopma <rp...@apache.org>
Authored: Tue May 10 02:38:32 2016 +0900
Committer: rpopma <rp...@apache.org>
Committed: Tue May 10 02:38:32 2016 +0900
----------------------------------------------------------------------
src/site/xdoc/manual/garbagefree.xml | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/logging-log4j2/blob/51ff83ce/src/site/xdoc/manual/garbagefree.xml
----------------------------------------------------------------------
diff --git a/src/site/xdoc/manual/garbagefree.xml b/src/site/xdoc/manual/garbagefree.xml
index 3b55012..bb16dd1 100644
--- a/src/site/xdoc/manual/garbagefree.xml
+++ b/src/site/xdoc/manual/garbagefree.xml
@@ -423,10 +423,11 @@ public void garbageFree() {
response time spikes.
</p>
<h4>Synchronous File Logging</h4>
- <p>With file synchronous logging, garbage-free logging still performs better, but the difference is less pronounced.
+ <p>With synchronous file logging, garbage-free logging still performs better than classic logging,
+ but the difference is less pronounced.
</p>
- <p>For both classic and garbage-free logging, synchronous file logging showed response times of 3-5 milliseconds
- even at loads of 100,000 messages/second.
+ <p>At a workload of 100,000 messages/second, classic logging max response time was a little over 2 milliseconds
+ where garbage-free logging was a little over 1 millisecond.
When the workload is increased to 300,000 messages/second, classic logging shows response time pauses of 6
milliseconds where the garbage-free response times were less than 3 milliseconds.
It may be possible to improve on this, we did not investigate further yet.</p>