| ▲ | jeroenhd 17 hours ago | ||||||||||||||||
12 seconds? It takes 7 seconds on my phone, in a wasm runtime using an older version of the encoder. From my experience throwing random JPEGs at it, it's 3 to 4 times smaller, that's a good chunk of data saved, which in turn is a lot of energy saved on visitors' radios being active. Unlike with jpeg, you don't need 85 or 95 percent on the quality score, 50 is more than good enough for most pictures on a website. If you're hosting images and want a fully lossless encoding the CPU time may become a factor, but if you're hosting user generated content, I don't think it's all that bad. Plus, you can just move the encoding part to the user side of the equation and pretend it's part of the upload progress bar if you're desperate to pay the power bill. | |||||||||||||||||
| ▲ | Aldipower 17 hours ago | parent [-] | ||||||||||||||||
The numbers above coming from a test run on one of my own servers serving and receiving user generated images. It is a Intel E5 56 CPU threads machine with DDR4 RAM. A single thread may be slower then your phone CPU cores, but that's what you find very often when running servers. | |||||||||||||||||
| |||||||||||||||||