Willy Tarreau bfd5946aa1 MINOR: ssl: add a global tunable for the max SSL/TLS record size ... Add new tunable "tune.ssl.maxrecord". Over SSL/TLS, the client can decipher the data only once it has received a full record. With large records, it means that clients might have to download up to 16kB of data before starting to process them. Limiting the record size can improve page load times on browsers located over high latency or low bandwidth networks. It is suggested to find optimal values which fit into 1 or 2 TCP segments (generally 1448 bytes over Ethernet with TCP timestamps enabled, or 1460 when timestamps are disabled), keeping in mind that SSL/TLS add some overhead. Typical values of 1419 and 2859 gave good results during tests. Use "strace -e trace=write" to find the best value. This trick was first suggested by Mike Belshe : http://www.belshe.com/2010/12/17/performance-and-the-tls-record-size/ Then requested again by Ilya Grigorik who provides some hints here : http://ofps.oreilly.com/titles/9781449344764/_transport_layer_security_tls.html#ch04_00000101		2013-02-21 07:53:13 +01:00
..
common	MEDIUM: tools: make str2sa_range support all address syntaxes	2013-02-20 17:29:30 +01:00
import	[MAJOR] replace ultree with ebtree in wait-queues	2008-06-24 08:17:16 +02:00
proto	MEDIUM: server: Break out set weight processing code	2013-02-13 10:53:40 +01:00
types	MINOR: ssl: add a global tunable for the max SSL/TLS record size	2013-02-21 07:53:13 +01:00