Mozjpeg 2.0

[Paul Mead]

Are there any plans to make use of the new Mozjpeg encoder within mod_pagespeed to get better compression for Jpeg consumers whose browsers don't support WebP?

Paul

[Jeff Kaufman]

If your compression system has parameters you can twiddle then one way
to get better compression is a brute force approach where you check
all the combinations of parameters and see which makes your particular
file smallest. This is what zopfli does, most of what pngcrush does,
and (I think) what mozjpeg does. You're trading substantial
processing time for a small increase in compression efficacy, so
whether this is worthwhile depends on how many times you're going to
serve the optimized file, what the compression gain is, and how much
slower it runs.

Do you know how much slower mozjpeg is? Has anyone run tests on this?
I know speed is not a major design goal for their project, but jpeg
encoding is fast enough that mozjpeg might still be reasonable.

> --
> 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/30f7d5e2-dc1c-4589-8ba1-d36b13c48e2b%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[Huibao Lin]

In addition to the issues that Jeff mentioned, we noticed that the images used for evaluating mozjpeg are quite different from typical ones in internet. We need evaluate it. Issue 961 has been created for it.

Huibao

To view this discussion on the web visit https://groups.google.com/d/msgid/mod-pagespeed-discuss/CAMJ6YUsyxwqQ%2BA9XFEq2PpXAFFeFvASFJ3uP7Wg8H-z6ajPybg%40mail.gmail.com.