Write about Tier 2 and JIT in "what's new 3.13" #114826
Merged
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.
Here's some text for "what's new 3.13" describing the Tier 2 and JIT architecture. It's not complete and missing references and details -- we can always improve it later, but suggestions for improvements right now are also welcome.
I used "JIT" as the headline, rather than "Tier 2" or "micro-ops", mostly because that's apparently the catchier phrase, and also because the JIT gives the best performance. (Numbers are TBD -- they will improve over the next few months as more of the optimization pipeline lands.)
It's a bit speculative because gh-114059 (@Fidget-Spinner's optimizer) hasn't landed yet -- we can wait merging this until it has.
Once this is in, I am hoping (based on an email exchange with @Yhg1s) that this work can also be highlighted in the alpha release announcements.
📚 Documentation preview 📚: https://cpython-previews--114826.org.readthedocs.build/