[
https://issues.apache.org/jira/browse/TS-2365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13837915#comment-13837915
]
ASF subversion and git services commented on TS-2365:
-----------------------------------------------------
Commit 42fc0106c26bb1ac5cf6bd03481f472c8c364d39 in branch refs/heads/master
from [~sunwei]
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=42fc010 ]
TS-2365: configure max TLS record size
The client can decipher the data only once it has received a full
record over SSL. The record size can have significant impact on the
page load time performance of the application. No limitation on
record size means that clients might have to download up to 16KB
of data before starting to process them, whereas very small records
incur a larger overhead due to record framing. The suggestion is
to configure the TLS record size to fit into a single TCP segment,
this can improve page load times on browsers located over high
latency or low bandwidth networks.
ref:
http://www.igvita.com/2013/10/24/optimizing-tls-record-size-and-buffering-latency/
> Configure max TLS record size
> -----------------------------
>
> Key: TS-2365
> URL: https://issues.apache.org/jira/browse/TS-2365
> Project: Traffic Server
> Issue Type: Improvement
> Components: Core, SSL
> Reporter: Wei Sun
> Assignee: James Peach
> Labels: A
> Fix For: 4.2.0
>
> Attachments: TS-2365.diff, ssl_maxrecordsize.diff,
> ssl_maxrecordsize2.diff
>
>
> The client can decipher the data only once it has received a full record over
> SSL. The record size can have significant impact on the page load time
> performance of the application. No limitation on record size means that
> clients might have to download up to 16KB of data before starting to process
> them, whereas very small records incur a larger overhead due to record
> framing. The suggestion is to configure the TLS record size to fit into a
> single TCP segment, this can improve page load times on browsers located over
> high latency or low bandwidth networks.
> ref:
> http://www.igvita.com/2013/10/24/optimizing-tls-record-size-and-buffering-latency/
--
This message was sent by Atlassian JIRA
(v6.1#6144)
