Skip to content
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

gh-115999: Update whats news for free-threaded 3.14 #131285

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

corona10
Copy link
Member

@corona10 corona10 commented Mar 15, 2025

@bedevere-app bedevere-app bot added docs Documentation in the Doc dir skip news awaiting core review labels Mar 15, 2025
@corona10 corona10 requested review from mpage, colesbury and itamaro March 15, 2025 14:06
@corona10 corona10 changed the title gh-11599: Update whats news for free-threaded 3.14 gh-115999: Update whats news for free-threaded 3.14 Mar 15, 2025
@corona10 corona10 requested a review from Yhg1s March 15, 2025 14:09
and 10-15% slower than the default build.

This work was done by many contributors, Matt Page, Neil Schemenauer,
Sam Gross, Thomas Wouters, Donghee Na, Kirill Podoprigora and Ken Jin.
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I also added the @Fidget-Spinner, because I remember his early design involvation while he worked at Quansight.

Copy link
Member

@Fidget-Spinner Fidget-Spinner Mar 15, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the main thing I did that is coming in 3.14 is the stackrefs. But we needed that for the intepreter anyways so it probably counts? Either way I can be left out if the others feel inclined to.

@corona10
Copy link
Member Author

corona10 commented Mar 15, 2025

Anyway, feel free to propose change as same as what we did for 3.13.

---------------------

Free-threaded CPython now supports :pep:`659` which is known
as the specializing adaptive interpreter, the execution mechanisms is almost same
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
as the specializing adaptive interpreter, the execution mechanisms is almost same
as the specializing adaptive interpreter. The execution mechanism is almost same

Comment on lines +325 to +326
With this change, the free-threaded CPython build achieve better performance
and 10-15% slower than the default build.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
With this change, the free-threaded CPython build achieve better performance
and 10-15% slower than the default build.
With this change, the free-threaded CPython build achieves better performance,
and is only 10-15% slower than the default build.

Maybe take out the slower part altogether ;-)

Comment on lines +322 to +323
as the default build, but at free-threaded CPython build, each thread maintains
a thread-local copy of specialized bytecode.
Copy link
Contributor

@StanFromIreland StanFromIreland Mar 15, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
as the default build, but at free-threaded CPython build, each thread maintains
a thread-local copy of specialized bytecode.
as the default build, however in a free-threaded CPython build, each thread
maintains a thread-local copy of specialized bytecode.


This work was done by many contributors, Matt Page, Neil Schemenauer,
Sam Gross, Thomas Wouters, Donghee Na, Kirill Podoprigora and Ken Jin.
Meta also provided significant engineering resources for performance benchmark and
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Meta also provided significant engineering resources for performance benchmark and
Meta also provided significant engineering resources for performance benchmarking and

I presume this is intended?

This work was done by many contributors, Matt Page, Neil Schemenauer,
Sam Gross, Thomas Wouters, Donghee Na, Kirill Podoprigora and Ken Jin.
Meta also provided significant engineering resources for performance benchmark and
design per thread specialized bytecode mechanisms.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
design per thread specialized bytecode mechanisms.
design of per thread specialized bytecode mechanisms.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
awaiting core review docs Documentation in the Doc dir skip news
Projects
Status: Todo
Development

Successfully merging this pull request may close these issues.

3 participants