Support » Plugin: Autoptimize » HTTP/2 max concurrent streams

  • Hi Frank,

    Finally getting my feet wet in HTTP/2 and searching for the best way to optimize for it. While some say that file aggregation should be abandoned, it looks like there is still a benefit to aggregation under HTTP/2 in that it can help keep the number of concurrent streams below the limit used by servers and browsers (typically 128 or 256 streams).

    It might be useful to have an option to set the max number of concurrent streams and then, if that is set, have AO only do sufficient aggregation to keep the total number of css and js files below that setting, aggregating into a small number of files rather than one single file.

    Take care,
    Shanna

    • This topic was modified 4 years, 8 months ago by wildmice.
Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Frank Goossens

    (@futtta)

    always great to hear from you @wildmice! interesting info there Shanna, the max nbr. of streams was something I hadn’t really thought about yet .. i’ll have to let this sink in a bit πŸ˜‰

    but there are two other things to keep in mind when doing HTTP/2 with or without AO:
    * HTTP/2 does not minify CSS/ JS
    * bigger files compress (deflate/ gzip) better then smaller files, so aggregation still makes sense

    based on the above, I would advice to go for the whitelist-approach (using the API), aggregating the “main” CSS/ JS i.e. the one used on (almost) every page. that way you’ll have an aggregated, minified, browser-cacheable file will be more “compressible” and you’ll bring your number of requests (streams) significantly down, allowing the remaining CSS/ JS to be served in the same HTTP/2 connection?

    have a nice weekend!
    frank

    Thread Starter wildmice

    (@wildmice)

    Hi Frank πŸ™‚

    In this case i inherited a large, very slow site with around 60 plugins and well over 200 resources to fetch. I wanted to get that down to 128 resources.

    Luckily, using AO the normal way was good in this situation, and it brought the number down to 138. Not perfect, but it reduced the load time from 14.5 to about 11.5 seconds.

    This is what got me thinking that for even larger sites it would be useful to be able to aggregate into several rather than one single file. So if we could simply specify the number of files we wanted for css and for js, then we could tweak things to bring the number of resources down to the point of optimum performance.

    Shanna

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘HTTP/2 max concurrent streams’ is closed to new replies.