Skip to content

Write about Tier 2 and JIT in "what's new 3.13" #114826

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Feb 1, 2024

Conversation

gvanrossum
Copy link
Member

@gvanrossum gvanrossum commented Jan 31, 2024

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/

@Fidget-Spinner
Copy link
Member

Fidget-Spinner commented Feb 1, 2024

There are in general two editorial directions we can take:

  1. Go into a bit more technical details, like what I chose to do in 3.11 https://docs.python.org/3/whatsnew/3.11.html#faster-cpython
  2. Leave the technical details out and give a high-level overview of the work. Write a blog post somewhere else to detail the technical stuff.

Personally, I am biased and in favour of 1. :). Anecdotally, it was quite well received among tech communities. People want to know exactly what it is that we improved, and the docs often form the authoritative source of information, and perhaps the only source of information some people know. I recall the 3.11 Faster CPython section being shared multiple times on various tech forums, and tech news sites.

Let me know what you think. I would love to collaborate on this. I like technical writing, just haven't had the time to do much recently.

@Fidget-Spinner
Copy link
Member

Fidget-Spinner commented Feb 1, 2024

I created gh-114863 to track whats new changes for faster cpython 3.13. Also #114862 as this PR but added more stuff.

@gvanrossum gvanrossum merged commit 2dea1cf into python:main Feb 1, 2024
@gvanrossum gvanrossum deleted the whatsnew branch February 1, 2024 16:54
@gvanrossum
Copy link
Member Author

@Fidget-Spinner I am fine with you writing a longer version. I've merged this one so I get partial credit. :-)

aisk pushed a commit to aisk/cpython that referenced this pull request Feb 11, 2024
(This will soon be superseded by Ken Jin's much more detailed version.)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants