2015-05-05 15:39 GMT+02:00 chen <gzche...@126.com>: > > This is v1 of the patchset the implementing the feature SSL Dynamic Record > Sizing, inspiring by Google Front End […] > > Any comments is welcome.
Nice! I've implemented that for Golang in the past and have ported it to C for you today. Although a single initial packet might seem more attractive in benchmarks, I found that sending two results in better catching parts of HEAD — which is what we want. Then you will notice some dancing around IW4, by which we've already sent about 5683 octets. Enough for me for a making a tradeoff here. 16k as ssl->buffer_size results in partially filled packets. A better default value could minimize the overhead (<0.5%) for that trailing PDUs. SSL libraries really should provide a function for computing overhead. -- Mark
nginx-1.9.1-SSL-dynamic-record-size-redux.patch
Description: Binary data
_______________________________________________ nginx-devel mailing list nginx-devel@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx-devel
