Async subinterpreters experiment #1965
Draft
Conversation
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
1 participant
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.
Since "subinterpreters" is now mainline as concurrent.interpreter in py3.14 (and reachable since 3.12, apparently), we can have true parallelism notwithstanding the GIL - especially since memoryview objects are uniquely zero-cost to transfer.
This PR will experiment with a new way to run batches of coroutines in async loops running in one subinterpreter in one thread each. This could increase throughput by something like 4x for the extremely high-bandwith case, where stream decoding (decrypt and decompress) makes IO CPU-bound.