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/18 14:41:09 UTC
logging-log4j2 git commit: html fix
Repository: logging-log4j2
Updated Branches:
refs/heads/master 72c809d1d -> cd0ae76b4
html fix
Project: http://git-wip-us.apache.org/repos/asf/logging-log4j2/repo
Commit: http://git-wip-us.apache.org/repos/asf/logging-log4j2/commit/cd0ae76b
Tree: http://git-wip-us.apache.org/repos/asf/logging-log4j2/tree/cd0ae76b
Diff: http://git-wip-us.apache.org/repos/asf/logging-log4j2/diff/cd0ae76b
Branch: refs/heads/master
Commit: cd0ae76b4f71268593b8f4e5345958881e17994e
Parents: 72c809d
Author: rpopma <rp...@apache.org>
Authored: Wed May 18 23:41:32 2016 +0900
Committer: rpopma <rp...@apache.org>
Committed: Wed May 18 23:41:32 2016 +0900
----------------------------------------------------------------------
.../apache/logging/log4j/core/async/perftest/ResponseTimeTest.java | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/logging-log4j2/blob/cd0ae76b/log4j-core/src/test/java/org/apache/logging/log4j/core/async/perftest/ResponseTimeTest.java
----------------------------------------------------------------------
diff --git a/log4j-core/src/test/java/org/apache/logging/log4j/core/async/perftest/ResponseTimeTest.java b/log4j-core/src/test/java/org/apache/logging/log4j/core/async/perftest/ResponseTimeTest.java
index 5d4334e..c584f7e 100644
--- a/log4j-core/src/test/java/org/apache/logging/log4j/core/async/perftest/ResponseTimeTest.java
+++ b/log4j-core/src/test/java/org/apache/logging/log4j/core/async/perftest/ResponseTimeTest.java
@@ -66,7 +66,7 @@ import org.apache.logging.log4j.core.util.Loader;
* <li>DO compare response time / latency spectrum at given loads.</li>
* <li>DO [repeatedly] sanity check and calibrate the benchmark setup to verify that it produces expected results for
* known forced scenarios. E.g. forced pauses of known size via ^Z or SIGSTOP/SIGCONT should produce expected response
- * time percentile levels. Attempting to load at >100% than achieved throughput should result in response time / latency
+ * time percentile levels. Attempting to load at >100% than achieved throughput should result in response time / latency
* measurements that grow with benchmark run length, while service time (if measured) should remain fairly flat well
* past saturation.</li>
* <li>DON'T use or report standard deviation for latency. Ever. Except if you mean it as a joke.</li>