You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "James Peach (JIRA)" <ji...@apache.org> on 2014/01/17 01:19:19 UTC
[jira] [Created] (TS-2503) dynamic TLS record size tuning
James Peach created TS-2503:
-------------------------------
Summary: dynamic TLS record size tuning
Key: TS-2503
URL: https://issues.apache.org/jira/browse/TS-2503
Project: Traffic Server
Issue Type: Improvement
Components: Performance, SSL
Reporter: James Peach
>From [~igrigorik] in TS-2365:
{code}
FWIW, I think you may be interested in this discussion:
- http://mailman.nginx.org/pipermail/nginx-devel/2013-December/004703.html
- http://mailman.nginx.org/pipermail/nginx-devel/2014-January/004748.html
In a nutshell, static record size introduces an inherent tradeoff between latency and throughput -- smaller records are good for latency, but hurt server throughput by adding bytes and CPU overhead. It would be great if we could implement a smarter strategy in ATS. The extra benefit is that it's one less knob to tune: the out-of-the-box experience would be better optimized for all ATS users, regardless of mix/type of traffic being proxies.
{code}
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)