-
Notifications
You must be signed in to change notification settings - Fork 29.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
http: cork/uncork before flushing pipelined res #3172
Conversation
Make sure that the pipelined response data will be written as less TCP packets as possible.
LGTM |
May I ask anybody to re-run the benchmarks to confirm that these -60% a just spurious? |
@indutny The http benchmarks vary a lot. That difference appears to just be some test variance.
The other difference is that |
@trevnorris cork calls are balanced, no spurious uncorking will happen... |
Cool. Then LGTM. |
Tests look good. Only external string bytes is failing. |
CI is green |
Landed in 184f09d, thank you everyone! |
Make sure that the pipelined response data will be written as less TCP packets as possible. PR-URL: #3172 Reviewed-By: Brian White <mscdex@mscdex.net> Reviewed-By: Trevor Norris <trev.norris@gmail.com>
Make sure that the pipelined response data will be written as less TCP packets as possible. PR-URL: #3172 Reviewed-By: Brian White <mscdex@mscdex.net> Reviewed-By: Trevor Norris <trev.norris@gmail.com>
Make sure that the pipelined response data will be written as less TCP
packets as possible.
Benchmark results (3 runs):
cc @trevnorris (we need performance WG)