• Nils Goroll's avatar
    When streaming, send headers if no body data available yet · 1df203a7
    Nils Goroll authored
    This is a TTFB optimization: I noticed that, when streaming, we would
    only sometimes send headers while waiting for more body data from the
    backend, depending on the amount of body data read ahead when reading
    the backend headers.
    
    The flush_head debug bit would avoid the delay, but it leads to an extra
    flush in all cases, even when we could send some body data down the line
    with the headers.
    
    This trivial patch peeks into the busy object to determine if the
    first ObjWaitExtend() is likely to block and, if so, issues a flush,
    which will cause the headers to be sent in addition to any initial data
    VDPs might have to send.
    1df203a7
Name
Last commit
Last update
.circleci Loading commit data...
.github Loading commit data...
bin Loading commit data...
doc Loading commit data...
etc Loading commit data...
include Loading commit data...
lib Loading commit data...
m4 Loading commit data...
man Loading commit data...
tools Loading commit data...
vmod Loading commit data...
.dir-locals.el Loading commit data...
.gitignore Loading commit data...
.lgtm.yml Loading commit data...
.syntastic_c_config Loading commit data...
.travis.yml Loading commit data...
CONTRIBUTING Loading commit data...
ChangeLog Loading commit data...
INSTALL Loading commit data...
LICENSE Loading commit data...
Makefile.am Loading commit data...
README.Packaging Loading commit data...
README.rst Loading commit data...
autogen.des Loading commit data...
autogen.sh Loading commit data...
configure.ac Loading commit data...
flint.lnt Loading commit data...
varnish-legacy.m4 Loading commit data...
varnish.m4 Loading commit data...
varnishapi-uninstalled.pc.in Loading commit data...
varnishapi.pc.in Loading commit data...
vtc.am Loading commit data...
wflags.py Loading commit data...