H2 and pagespeed

[Stephen Reese]

Any plans to provide recommendations for early HTTP/2 adopters that use modpagespeed? I understand every site is unique but high-level, any thoughts?

Should sharding be disabled?

Will it still be advantageous to combine resources? What if push is used for CSS and JS assets?

Other thoughts?

As HTTP/1.1 clients would no longer benefit from these optimizations if they are disable, guess it would depend on the number of clients whom visit your site that support HTTP/2.

Thanks,

Stephen

[Jeff Kaufman]

For use with h2 we recommend:

* turn off domain sharding

* turn off resource combining: css, js, images (spriting)

We're planning to make this automatic in a later version, but you need to do it manually for now.

--
You received this message because you are subscribed to the Google Groups "mod-pagespeed-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mod-pagespeed-di...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/mod-pagespeed-discuss/CAC6_mQNQgw-aUzXSaaLvycSx4VRUrrdaTP6MKagpi_Xrnv-GDQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Joshua Marantz]

It's not clear that combining is made obsolete with http2 at this time.  See the recent post from the people behind Khan Academy:   http://engineering.khanacademy.org/posts/js-packaging-http2.htm

Note that PageSpeed does not combine arbitrarily, but bounds the size of the combined files based on experiments we ran earlier, which is similar to what Khan did manually.  However, turning off sharding when running under H2 sounds great.

To view this discussion on the web visit https://groups.google.com/d/msgid/mod-pagespeed-discuss/CAMJ6YUvNrBw5XNYvMyAmYtDOAy%2B%3D2rA1XTJmgJs9Vso1zkXYBw%40mail.gmail.com.