Except in (mostly upstream) traffic (or downstream when having lots of cache validations succeed). In this example: HTTP/1.1 upstream: 18.33MB HTTP/2 upstream: 2.87MB (space savings 85.65%) -Stefan > Am 22.01.2018 um 15:14 schrieb Eric Covener <covener@xxxxxxxxx>: > > On Mon, Jan 22, 2018 at 9:02 AM, Hajo Locke <Hajo.Locke@xxxxxx> wrote: >> >> >> Am 22.01.2018 um 14:38 schrieb Eric Covener: >>>> >>>> but i never expected that my winner in this test is mod_php. also there >>>> was lowest >>>> loadavg. >>> >>> I don't think the motivations to pull the PHP interpreter out of the >>> webserver process is performance -- that's one of the costs. >> >> yes. my statement was made in the context of http2 > mpm_prefork > mod_php > >> "H2Worker 1" >> basically mod_php is a fast technique and depending on purpose a good >> solution. > > I think with very little latency and no dependencies in one flow it > will be hard to see h2 benefits. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx > For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|