Guetzli with time chart
Guetzli sacrifices encoding time. To illustrate the pedestrian nature of Guetzli, let’s test how long the encoding takes.
The chart below shows how long it takes to encode photographs with various MPs. Tests were performed using an Intel Core i5-2500K processor.
That’s correct, it took more than 30 minutes to encode a single 36 Megapixel JPEG image. Most image collections won’t be full of 36MP images of course. But even an 18MP image took more than 6 minutes to process. It’s incredibly CPU intensive.
You’re probably wondering about the mysterious C-36MP in the chart. That is MozJPEG (cjpeg) processing the 36MP image in a mere 7 seconds. Contrast that with Guetzli which takes 1,848 seconds. Wow!
Guetzli uses a single core. If your machine has lots of cores, you might think you could make significant time savings by running multiple instances of the software. But remember, Guetzli uses bucket loads of RAM when processing images with high MPs. For example, it peaked at over 5GB of RAM when tackling the 36MP image. You don’t want to be hitting swap when encoding.
Pages in this article:
Page 1 – Introduction
Page 2 – Guetzli – Compression charts
Page 3 – Guetzli – Time chart
Page 4 – MozJPEG – Compression charts
Page 5 – MozJPEG – Time chart
Page 6 – Lepton – Compression charts
Page 7 – Lepton – Time chart
Page 8 – Summary