-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
JPEG-XL: decoding is extremely slow #179
Comments
Yea, I sadly didn't write the decoder, that is a format that scares me. :) I wish i had infinite time to optimize them, but working on it |
No worries, this is just for the backlog. Keep up the great work! |
I've been doing some profiling on jxl-oxide and the author has been continuously working on improving performance, including based on my findings. A 50x slowdown compared to JPEG is unexpected. I suggest you submit the file that causes such a large runtime to jxl-oxide issue tracker; it is possible that it is hitting an abnormally slow codepath that would be easy to optimize. |
I also realized I was using a very ancient version, updated in 23c8bb1 so it might have lacked the optimizations above, so they should probably be rerun |
It seems parallel decoding for jxl-oxide was not enabled. Enabling it should help performance: 72f16e4 |
I understand that zune-image uses jxl-oxide for JPEG-XL decoding and it's probably them are to blame, but since zune-image aims to be fast on all formats (hopefully, and eventually), I'm firing this issue here.
Again, here are some benchmarks:
The text was updated successfully, but these errors were encountered: