----- Original Message ----- > TS-1365 Update documentation
This should've been in the same commit as the adding of the feature. > Project: http://git-wip-us.apache.org/repos/asf/trafficserver/repo > Commit: http://git-wip-us.apache.org/repos/asf/trafficserver/commit/a74ef5a0 > Tree: http://git-wip-us.apache.org/repos/asf/trafficserver/tree/a74ef5a0 > Diff: http://git-wip-us.apache.org/repos/asf/trafficserver/diff/a74ef5a0 > > Branch: refs/heads/master > Commit: a74ef5a049347a864a0597364d3575ec297eeeb5 > Parents: eccb33c > Author: Leif Hedstrom <zw...@apache.org> > Authored: Thu Jan 2 15:18:52 2014 -0700 > Committer: Leif Hedstrom <zw...@apache.org> > Committed: Thu Jan 2 15:30:53 2014 -0700 > > ---------------------------------------------------------------------- > .../configuration/records.config.en.rst | 20 ++++++++++++++++++++ > 1 file changed, 20 insertions(+) > ---------------------------------------------------------------------- > > > http://git-wip-us.apache.org/repos/asf/trafficserver/blob/a74ef5a0/doc/reference/configuration/records.config.en.rst > ---------------------------------------------------------------------- > diff --git a/doc/reference/configuration/records.config.en.rst > b/doc/reference/configuration/records.config.en.rst > index c92f351..08aaf1a 100644 > --- a/doc/reference/configuration/records.config.en.rst > +++ b/doc/reference/configuration/records.config.en.rst > @@ -2225,6 +2225,26 @@ Sockets > > Same as the command line option ``--accept_mss`` that sets the MSS for > all incoming requests. > > +.. ts:cv:: CONFIG proxy.config.net.poll_timeout INT 0 > + > + Same as the command line option ``--poll_timeout``, or ``-t``, which > + specifies the timeout used for the polling mechanism used. This timeout > is > + always in milliseconds (ms). On Linux, this is the timeout to > + ``epoll_wait()``. The default value is ``10`` on all platforms except > + Solaris, where it is ``30``. *Why* is it different on Solaris? > + Changing this configuration can reduce CPU usage on an idle system, since > + periodic tasks gets processed at these intervals. On busy servers, this > + overhead is diminished, since polled events triggers more > + frequently. However, increasing the setting can also introduce additional > + latency for certain operations, and timed events. It's recommended not to > + touch this setting unless your CPU usage is unacceptable at idle > + workload. Some alternatives to this could be:: > + > + Reduce the number of worker threads (net-threads) > + Reduce the number of disk (AIO) threads > + We should link here to the appropriate settings that would require tuning, or to the (still rather poor) performance tuning document. > + > Undocumented > ============ > > > -- Igor Galić Tel: +43 (0) 664 886 22 883 Mail: i.ga...@brainsware.org URL: http://brainsware.org/ GPG: 8716 7A9F 989B ABD5 100F 4008 F266 55D6 2998 1641
