Rely on subprocess.Popen pipesize parameter rather than custom code for seting pipe size.#179
Merged
Conversation
…or seting pipe size.
Collaborator
|
Awesome! (And wow, already six years since #36 (comment) ...) |
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.
As soon as I found the problem with pipes being 64KB by default and xopen issuing 128KB reads and writes I made a PR to CPython allowing to set the pipesize on subprocess.
Now we can finally pick the fruits of that labour!
As a side note, this is so useful. Forget bash. Pipe your programs together using python and set pipesize to 1MB. Enjoy much better speeds!