Warning: this page is quite out of date now.
As part of encoding improvements (mostly in #419), we have collected encoding performance statistics for 4 still test pictures using the current crop of codec code (pre-release version 0.13).
These encodings are also used when a video encoding is selected as primary encoding, this is done to optimize bandwidth and CPU usage: video encodings require a full frame every time, so we use still picture encodings for smaller regions and for automatic lossless refresh.
|Mode||Desktop 2560x1600||Browser 1920x1080||Diagram 640x800||Small Alpha 64x48|
|webp||Cython||TEXT + lossless||100||0||0.1||4.9||0.6||0.7||0.3||1.6||0.0||24.7|
|webp||Cython||TEXT + lossless||100||100||2.3||5.9||27.8||1.3||27.2||1.9||1.5||26.9|
- all tests were performed on an AMD FX-8150 (octa-core 3GHz AMD CPU)
- video encodings are not included, and should generally be preferred to the single picture encodings shown here
- this shows both speed in mega pixels per second (higher is better), and compression ratio (lower is better)
- Low quality at low speed doesn't really make much sense, so some values have been omitted
- changing the
webppreset does not affect speed or output size much, it probably does affect the perceived picture quality (seems best to stick with TEXT to ensure that text remains readable)
- The new
webpencoder seems to perform about the same with speeds >50%, only low speed is really slow, and lossless is unbearably slow (it can take more than 30 seconds to encode a single frame using lossless + low speed!)
- quality is not the same for each encoder, some have lossless modes others not, etc..
- for data showing the differences between the various
pngcompression types (
DEFAULT), see ticket:419#comment:6
You can find a much more detailed analysis (but which is limited to lossy formats in
YUV420 colourspace mode...) here: Lossy Compressed Image Formats Study