[TS-2503] Dynamic TLS record size tuning

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 5.2.0
• Component/s: Performance, SSL
• Assignee: Sudheer Vinukonda
• Reporter: James Peach
• Created: 17/Jan/14 00:18
• Updated: 14/Jun/16 16:43
• Resolved: 05/Nov/14 22:03

Description

From Ilya Grigorik in TS-2365:

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.

Issue Links

• is related to: TS-4424 proxy.config.ssl.max_record_size=-1 (dynamic rec size) can cause out-of-bound memory access