async logging manual page: added disclaimer about async logging when CPU resources are scarce
Project: http://git-wip-us.apache.org/repos/asf/logging-log4j2/repo Commit: http://git-wip-us.apache.org/repos/asf/logging-log4j2/commit/4dc028fc Tree: http://git-wip-us.apache.org/repos/asf/logging-log4j2/tree/4dc028fc Diff: http://git-wip-us.apache.org/repos/asf/logging-log4j2/diff/4dc028fc Branch: refs/heads/LOG4J-1181 Commit: 4dc028fc6946456c9d0f8a828853f9f029596ca1 Parents: 856e034 Author: rpopma <rpo...@apache.org> Authored: Wed May 25 08:35:53 2016 +0900 Committer: rpopma <rpo...@apache.org> Committed: Wed May 25 08:35:53 2016 +0900 ---------------------------------------------------------------------- src/site/xdoc/manual/async.xml | 2 ++ 1 file changed, 2 insertions(+) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/logging-log4j2/blob/4dc028fc/src/site/xdoc/manual/async.xml ---------------------------------------------------------------------- diff --git a/src/site/xdoc/manual/async.xml b/src/site/xdoc/manual/async.xml index 3baf01d..373b5f4 100644 --- a/src/site/xdoc/manual/async.xml +++ b/src/site/xdoc/manual/async.xml @@ -109,6 +109,8 @@ implementations should be designed with asynchronous use in mind, and either take a snapshot of their parameters at construction time, or document their thread-safety characteristics. </li> + <li>If your application is running on a single core, starting another thread is not likely + to give better performance.</li> <li> If the <em>sustained rate</em> at which your application is logging messages is faster than the maximum sustained throughput of the underlying appender, the queue will fill up and the
