We are JPEG-compressing a large quantity of images on the fly.
This is a server-side process to interactively prepare images to be sent to the clients' browsers.
Using progressive compression would improve the user experience.
I know that this compression requires more computation for decompression, but that's not an issue.
I'd like to know if progressive compression is more costly too and how much (without running my own serie of tests and benchmarks).
After running benchmarks I noticed that generating a JPEG requires an amount of cpu time that is roughly proportional to the number of progressive scans
What I stated in my question...
Using progressive compression would improve the user experience
is actually false since most browsers show the image only when completely loaded by the client.