gh-125985: Fix cmodule_function() scaling benchmark#128460
Merged
colesbury merged 2 commits intopython:mainpython/cpython:mainfrom Jan 3, 2025
colesbury:gh-125985-scaling-benchcolesbury/cpython:gh-125985-scaling-benchCopy head branch name to clipboard
Merged
gh-125985: Fix cmodule_function() scaling benchmark#128460colesbury merged 2 commits intopython:mainpython/cpython:mainfrom colesbury:gh-125985-scaling-benchcolesbury/cpython:gh-125985-scaling-benchCopy head branch name to clipboard
cmodule_function() scaling benchmark#128460colesbury merged 2 commits intopython:mainpython/cpython:mainfrom
colesbury:gh-125985-scaling-benchcolesbury/cpython:gh-125985-scaling-benchCopy head branch name to clipboard
Conversation
Add a separate benchmark that measures the effect of `_PyObject_LookupSpecial()` on scaling. In the process of cleaning up the scaling benchmarks for inclusion, I unintentionally changed the "cmodule_function" benchmark to pass an `int` to `math.floor()` instead of a `float`, which causes it to use the `_PyObject_LookupSpecial()` code path. `_PyObject_LookupSpecial()` has its own scaling issues that we want to measure separately from calling a function on a C module.
Contributor
Author
|
When combined with #128164:
|
Co-authored-by: mpage <mpage@cs.stanford.edu>
WolframAlph
pushed a commit
to WolframAlph/cpython
that referenced
this pull request
Jan 4, 2025
…28460) Add a separate benchmark that measures the effect of `_PyObject_LookupSpecial()` on scaling. In the process of cleaning up the scaling benchmarks for inclusion, I unintentionally changed the "cmodule_function" benchmark to pass an `int` to `math.floor()` instead of a `float`, which causes it to use the `_PyObject_LookupSpecial()` code path. `_PyObject_LookupSpecial()` has its own scaling issues that we want to measure separately from calling a function on a C module.
srinivasreddy
pushed a commit
to srinivasreddy/cpython
that referenced
this pull request
Jan 8, 2025
…28460) Add a separate benchmark that measures the effect of `_PyObject_LookupSpecial()` on scaling. In the process of cleaning up the scaling benchmarks for inclusion, I unintentionally changed the "cmodule_function" benchmark to pass an `int` to `math.floor()` instead of a `float`, which causes it to use the `_PyObject_LookupSpecial()` code path. `_PyObject_LookupSpecial()` has its own scaling issues that we want to measure separately from calling a function on a C module.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Add a separate benchmark that measures the effect of
_PyObject_LookupSpecial()on scaling.In the process of cleaning up the scaling benchmarks for inclusion, I unintentionally changed the
cmodule_functionbenchmark to pass aninttomath.floor(), which causes it to use the_PyObject_LookupSpecial()code path._PyObject_LookupSpecial()has its own scaling issues that we want to measure separately.