perf: faster jxl decoding #681
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi Jeremy,
The current JXL decoding speed is kind of slow. It looks like rust jxl-oxide doesn't support simd or threads currently, but I was able to optimize the binary with
wasm-opt -O3which cut the size of the wasm file from 2.0 MB to 1.7 MB and seems to speed up decoding by 19% on some test images.It's still slow, but the speed up makes it somewhat more tolerable (~2.1s to ~1.7s). By comparison JPEG decodes in about 0.2s on these images.
As an aside, I heard from internet forums that Google Research might be producing a JXL rust decoder implementation for Firefox, but I don't know what the status is of that. I presume it'll be pretty fast when it's ready.
Will