ENH: use PyMem_RawMalloc instead of system allocator for better performance on free-threading (#31503)#31531
Merged
Conversation
…rmance on free-threading (numpy#31503)
charris
added
01 - Enhancement
08 - Backport
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
2 participants
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.
Backport of #31503.
PR summary
Fixes #28454
This PR replaces usage of system allocator
mallocwithPyMem_RawMallocand friends for better performance on free-threading where mimalloc is used as the underlying allocator.AI Disclosure
I used Claude to find all the places where the replacement makes sense.