Uh oh!
There was an error while loading. Please reload this page.
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 resultsCPython 3.13t resultsnogil fork (3.9) resultsAs 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. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
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_ATTRnot yet using deferred reference counting) and when accessing thread-local data.