Resolves #1426 - Updating JavaDoc.

Signed-off-by: WalkerWatch <ctwalker@gmail.com>
This commit is contained in:
WalkerWatch 2017-03-29 11:54:33 -04:00
parent a9b4e2422a
commit 071cf19f2b
2 changed files with 2 additions and 2 deletions

View File

@ -129,7 +129,7 @@ import org.eclipse.jetty.util.thread.Scheduler;
* <li>call the {@link #getDefaultConnectionFactory()} {@link ConnectionFactory#newConnection(Connector, org.eclipse.jetty.io.EndPoint)} * <li>call the {@link #getDefaultConnectionFactory()} {@link ConnectionFactory#newConnection(Connector, org.eclipse.jetty.io.EndPoint)}
* method to create a new Connection instance.</li> * method to create a new Connection instance.</li>
* </ol> * </ol>
* The default number of acceptor tasks is the minimum of 1 and half the number of available CPUs. Having more acceptors may reduce * The default number of acceptor tasks is the minimum of 1 and the number of available CPUs divided by 8. Having more acceptors may reduce
* the latency for servers that see a high rate of new connections (eg HTTP/1.0 without keep-alive). Typically the default is * the latency for servers that see a high rate of new connections (eg HTTP/1.0 without keep-alive). Typically the default is
* sufficient for modern persistent protocols (HTTP/1.1, HTTP/2 etc.) * sufficient for modern persistent protocols (HTTP/1.1, HTTP/2 etc.)
*/ */

View File

@ -71,7 +71,7 @@ import org.eclipse.jetty.util.thread.Scheduler;
* that these callbacks may do some non-blocking IO work, but will always dispatch to the * that these callbacks may do some non-blocking IO work, but will always dispatch to the
* {@link Executor} service any blocking, long running or application tasks. * {@link Executor} service any blocking, long running or application tasks.
* <p> * <p>
* The default number of selectors is equal to the number of processors available to the JVM, * The default number of selectors is equal to half of the number of processors available to the JVM,
* which should allow optimal performance even if all the connections used are performing * which should allow optimal performance even if all the connections used are performing
* significant non-blocking work in the callback tasks. * significant non-blocking work in the callback tasks.
*/ */