Protip: Do not use progressive JPEGs to save disk space or network transmission speed. If you want progressive loading, ok, but otherwise, progressive jpegs require disproportionate amounts of CPU effort to decode vs. the savings. E.g. on mobile you're paying with power.
-
-
oh man i never thought about the comparative cost of the different png filters. i wonder how much Gzip vs Brotli factors in here, for that matter... like if people are just applying brotli to all their files on server, even png and jpeg, how much power does that waste
-
libpng still doesn’t have SIMD code for defiltering on x86, amazingly :(
End of conversation
New conversation -
-
-
No, Optipng is a pure win. Gzip inflate is the biggest cost. Also, most optimized PNGs don't even use filtering. PNG interlacing is pretty bad, but mostly because it creates less compressible data, which is again more work for inflate.
-
When I measured, filtering was about the same cost as inflate. I could pipeline them to hide the latency. It’s true that inflate was usually the bottleneck in that case, but it still saves power to not have to defilter.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.