-
-
Notifications
You must be signed in to change notification settings - Fork 383
perf:remove isinstance check #3704
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
Merged
d-v-b
merged 7 commits into
zarr-developers:main
from
d-v-b:perf/remove-isinstance-check
Feb 13, 2026
+3
−9
Merged
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
eee0079
remove isinstance check inside bytescodec
d-v-b 6722343
remove isinstance check inside bytescodec
d-v-b 7cb16f3
Merge branch 'main' into perf/remove-isinstance-check
d-v-b 4105972
changelog
d-v-b c62d077
Merge branch 'main' into perf/remove-isinstance-check
d-v-b f0d4b2e
Merge branch 'main' into perf/remove-isinstance-check
d-v-b ca35193
Merge branch 'main' into perf/remove-isinstance-check
d-v-b File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1 @@ | ||
| Remove an expensive `isinstance` check from the bytes codec decoding routine. |
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can we just have
as_array_likebecomeas_ndarray_like?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
you mean just rename the variable? We have to choose where the surprise is: at the
as_array_likecall (surprising if it returns an ndarraylike) orfrom_ndarray_like(surprising if it accepts an arraylike) call. I don't see much of a difference here, but happy to rename if you feel stronglyUh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(this is why I shouldn't reply when half-asleep at night)
Apologies for the confusion. Can we not have
Buffer.as_ndarray_like()that makes the bytes ready for the codec pipeline in the form the codec pipeline needs it i.e.NDArrayLike? That way it is type safe and performant.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ah sorry so a new method, that ensures that the contents of the buffer are an ndarray? yeah I think that should be easy to add!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is it OK if we spin that out into a separate issue?
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure, but isn't the needed change just modifying
as_array_liketo callnp.asanyarrayin the CPU bufferThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
doesn't this requires changing the
as_array_likemethod for gpu buffer too, and/or the method on the abc?zarr-python/src/zarr/core/buffer/core.py
Line 234 in e03cfc8
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ya, up to you as to when you want to fix it...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Buffer is public api so I don't think we want to change that as part of a performance fix.