[
https://issues.apache.org/jira/browse/TS-2365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13837632#comment-13837632
]
Wei Sun commented on TS-2365:
-----------------------------
If you're sure that there isn't thread-safe issue, it looks good to me.
Verified in my test env.
CONFIG proxy.config.ssl.max_record_size INT 1420
2 6 1386073253.6491 (0.0000) C>S V3.1(1) ChangeCipherSpec
2 7 1386073253.6491 (0.0000) C>S V3.1(36) Handshake
2 8 1386073253.6509 (0.0018) S>C V3.1(1) ChangeCipherSpec
2 9 1386073253.6509 (0.0000) S>C V3.1(36) Handshake
2 10 1386073253.9012 (0.2502) C>S V3.1(211) application_data
2 11 1386073253.9096 (0.0084) S>C V3.1(557) application_data
2 12 1386073253.9097 (0.0000) S>C V3.1(1440) application_data
2 13 1386073253.9097 (0.0000) S>C V3.1(1440) application_data
2 14 1386073253.9097 (0.0000) S>C V3.1(1440) application_data
2 15 1386073253.9097 (0.0000) S>C V3.1(1440) application_data
2 16 1386073254.1601 (0.2503) S>C V3.1(1440) application_data
2 17 1386073254.1601 (0.0000) S>C V3.1(560) application_data
2 18 1386073254.1601 (0.0000) S>C V3.1(1440) application_data
2 19 1386073254.1601 (0.0000) S>C V3.1(1440) application_data
2 20 1386073254.1604 (0.0003) S>C V3.1(1440) application_data
2 21 1386073254.1604 (0.0000) S>C V3.1(1440) application_data
2 22 1386073254.1604 (0.0000) S>C V3.1(1440) application_data
2 23 1386073254.1604 (0.0000) S>C V3.1(1440) application_data
2 24 1386073254.1605 (0.0000) S>C V3.1(1440) application_data
2 25 1386073254.1605 (0.0000) S>C V3.1(1440) application_data
2 26 1386073254.1998 (0.0393) S>C V3.1(1440) application_data
2 27 1386073254.1998 (0.0000) S>C V3.1(1440) application_data
2 28 1386073254.4105 (0.2106) S>C V3.1(1440) application_data
> 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)
