[
https://issues.apache.org/jira/browse/TS-153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13817792#comment-13817792
]
Bryan Call commented on TS-153:
-------------------------------
Production "debug" output running with 20 threads and the limit set to 500.
Sill need to make changes to the configuration to make it more user friendly.
{code}
[Nov 8 22:46:05.773] Server {0x2b8803f4e700} ERROR: keep alive lru size: 506
max: 500 total: 571
[Nov 8 22:46:05.787] Server {0x2b8801d823a0} ERROR: keep alive lru size: 513
max: 500 total: 568
[Nov 8 22:46:05.788] Server {0x2b8808504700} ERROR: keep alive lru size: 509
max: 500 total: 571
[Nov 8 22:46:05.797] Server {0x2b8808b0a700} ERROR: keep alive lru size: 505
max: 500 total: 561
[Nov 8 22:46:05.889] Server {0x2b8808403700} ERROR: keep alive lru size: 509
max: 500 total: 552
[Nov 8 22:46:05.889] Server {0x2b8803847700} ERROR: keep alive lru size: 504
max: 500 total: 560
[Nov 8 22:46:05.889] Server {0x2b8803b4a700} ERROR: keep alive lru size: 515
max: 500 total: 562
[Nov 8 22:46:05.889] Server {0x2b8808605700} ERROR: keep alive lru size: 507
max: 500 total: 564
[Nov 8 22:46:05.889] Server {0x2b8803948700} ERROR: keep alive lru size: 510
max: 500 total: 572
{code}
> "Dynamic" keep-alive timeouts
> -----------------------------
>
> Key: TS-153
> URL: https://issues.apache.org/jira/browse/TS-153
> Project: Traffic Server
> Issue Type: New Feature
> Components: Core
> Reporter: Leif Hedstrom
> Assignee: Bryan Call
> Priority: Minor
> Labels: A
> Fix For: 4.2.0
>
> Attachments: ts153.diff
>
>
> (This is from a Y! Bugzilla ticket 1821593, adding it here. . Originally
> posted by Leif Hedstrom on 2008-03-19):
> Currently you have to set static keep-alive idle timeouts in TS, e.g.
> CONFIG proxy.config.http.keep_alive_no_activity_timeout_in INT 8
> CONFIG proxy.config.http.keep_alive_no_activity_timeout_out INT 30
> even with epoll() in 1.17.x, this is difficult to configure, and put an
> appropriate timeout. The key here is that the
> settings above need to assure that you stay below the max configured number
> of connections, e.g.:
> CONFIG proxy.config.net.connections_throttle INT 75000
> I'm suggesting that we add one (or two) new configuration options, and
> appropriate TS code support, to instead of
> specifying timeouts, we specify connection limits for idle KA connections.
> For example:
> CONFIG proxy.config.http.keep_alive_max_idle_connections_in INT 50000
> CONFIG proxy.config.http_keep_alive_max_idle_connections_out INT 5000
> (one still has to be careful to leave head-room for active connections here,
> in the example above, 20000 connections
> could be active, which is a lot of traffic).
> These would override the idle timeouts, so one could use the max_idle
> connections for incoming (client) connections,
> and the idle timeouts for outgoing (origin) connections for instance.
> The benefit here is that it makes configuration not only easier, but also a
> lot safer for many applications.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
