{"push_id":1433015933,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"422bbd21c28e116e90b23f46f96caafa97e9bf1f","before":"0053b8e33975047e82afee535f47a96ceac4ac67","commits":[{"sha":"422bbd21c28e116e90b23f46f96caafa97e9bf1f","author":{"name":"Denis Denisov","email":"f767ef6560eb65bc13fd37fb8eddc0197f06f413@gmail.com"},"message":"NGINX support for Dynamic TLS Record Resizing\n\nWhat we do now:\nWe use a static record size of 4K. This gives a good balance of latency and\nthroughput.\n\nOptimize latency:\nBy initialy sending small (1 TCP segment) sized records, we are able to avoid\nHoL blocking of the first byte. This means TTFB is sometime lower by a whole\nRTT.\n\nOptimizing throughput:\nBy sending increasingly larger records later in the connection, when HoL is not\na problem, we reduce the overhead of TLS record (29 bytes per record with\nGCM/CHACHA-POLY).\n\nLogic:\nStart each connection with small records (1369 byte default, change with\nssl_dyn_rec_size_lo). After a given number of records (40, change with\nssl_dyn_rec_threshold) start sending larger records (4229, ssl_dyn_rec_size_hi).\nEventually after the same number of records, start sending the largest records\n(ssl_buffer_size).\nIn case the connection idles for a given amount of time (1s,\nssl_dyn_rec_timeout), the process repeats itself (i.e. begin sending small\nrecords again).","distinct":true,"url":"https://api.github.com/repos/nginx-modules/ngx_ssl_dyn_rec_size/commits/422bbd21c28e116e90b23f46f96caafa97e9bf1f"}]}
{"actor":{"display_login":"denji"}}