-
-
Notifications
You must be signed in to change notification settings - Fork 31.4k
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-125985: Add free threading scaling micro benchmarks #125986
Conversation
These consist of a number of short snippets that help identify scaling bottlenecks in the free threaded interpreter. The current bottlenecks are in calling functions in benchmarks that call functions (due to `LOAD_ATTR` not yet using deferred reference counting) and when accessing thread-local data.
Some results below: CPython 3.14t results
CPython 3.13t results
nogil fork (3.9) results
As mentioned in the PR description, we have known scaling issues related to The 3.13 release avoids the Note that small variations (e.g. 8.8x vs. 10.4x) are not meaningful. |
Co-authored-by: Tomas R. <tomas.roun8@gmail.com>
…125986) These consist of a number of short snippets that help identify scaling bottlenecks in the free threaded interpreter. The current bottlenecks are in calling functions in benchmarks that call functions (due to `LOAD_ATTR` not yet using deferred reference counting) and when accessing thread-local data.
…125986) These consist of a number of short snippets that help identify scaling bottlenecks in the free threaded interpreter. The current bottlenecks are in calling functions in benchmarks that call functions (due to `LOAD_ATTR` not yet using deferred reference counting) and when accessing thread-local data.
These consist of a number of short snippets that help identify scaling bottlenecks in the free threaded interpreter.
The current bottlenecks are in calling functions in benchmarks that call functions (due to
LOAD_ATTR
not yet using deferred reference counting) and when accessing thread-local data.