Speed up and simplify GIF optimization - #10074
Merged
Merged
Conversation
akx
marked this pull request as ready for review
September 28, 2026 10:22
radarhere
reviewed
Sep 28, 2026
radarhere
approved these changes
Sep 28, 2026
This file contains hidden or 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.
While working on #10072, I was looking for uses of
ImageMatharound Pillow, and this seemed like a pretty complex construction and there indeed was a simpler one lurking in there... 😄ImageChopswas optimized in 4b5a6e3 andImage.pointwould be optimized by #9743. #9829 would improve (though currently slightly slow down 😞) quantization accuracy.There are no new tests or benchmarks committed; the test added in #7568 covers this.
This also requires less intermediate images, so peak memory use decreases too (30% to 80% on my machine, depending on whether we're talking shared palette or a per-frame one).
I benchmarked this locally:
The per-frame-palette case doesn't get optimized much since it's dominated by palette quantization, not this.