On Fri, Jan 17, 2014 at 9:50 AM, Willy Tarreau <w...@1wt.eu> wrote:
> > Yup, that sounds like an interesting strategy. The only thing to note is
> > that you should consider resetting the record size after some idle
> timeout
> > -- same logic as slow-start after idle.
>
> We wouldn't even need this because the only reason for observing an idle
> period is that there's a new request/response cycle, and buffer flags are
> reset upon each new request so the "streamer" flag will automatically
> disappear.
>
Gotcha, makes sense.
> > For changing the actual record
> > size, I don't believe there is much more to it than just changing how
> much
> > you write into the record vs. number of records you emit: last patch for
> > tuning record size accomplishes this by setting a max on "try" byte
> count.
>
> Indeed, but Emeric has found something interesting. It seems there's a
> tunable
> in recent OpenSSL versions ("mtu" or something like this) with which you
> can
> adjust how many bytes are sent over the wire in a single record. So it
> might
> end up being even more precise than playing with the max on "try". We'll
> see.
> Anyway your suggestion is very interesting and merits some experimentation!
> Lowering time to first byte is always something useful to get users happy!
Ah, interesting. Doing a bit more digging on this end, I see
"SSL_set_max_send_fragment", albeit that's from back in 2005. Is that what
you guys are looking at?
https://github.com/openssl/openssl/commit/566dda07ba16f9d3b9774fd5c8d526d7cc93f179
ig
