bpo-30919: shared memory allocation performance regression in multiprocessing#2708
Merged
Conversation
…multiprocessing
|
@pitrou, thanks for your PR! By analyzing the history of the files in this pull request, we identified @benjaminp, @shibturn and @abalkin to be potential reviewers. |
pitrou
changed the title
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
3 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.
There is a huge regression in creating shared memory arenas in 3.x compared to 2.7. Python 2.7 created an anonymous memory mappping, while 3.x mmaps an actual file.
ftruncateinstead of actual writes to create a sparse file where supported.tmpfs(or equivalent) rather than a persistent storage-backed directory.https://bugs.python.org/issue30919