Optimizing when reading arrays rather than images from tiff files #1423
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
Specifically, if we want a numpy array, reading a jpeg or jp2k encoded tile as the raw image bytes and then decoding it with simplejpeg or PIL is slower than having libtiff decode it. If, however, we want to serve a jpeg, it is quicker to never decode it, so this code path remains the same.
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.
Specifically, if we want a numpy array, reading a jpeg encoded tile as the raw image bytes and then decoding it with simplejpeg or PIL is slower than having libtiff decode it. If, however, we want to serve a jpeg, it is quicker to never decode it, so this code path remains the same.