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-96636: Remove all uses of NOTRACE_DISPATCH #96643
GH-96636: Remove all uses of NOTRACE_DISPATCH #96643
Conversation
Misc/NEWS.d/next/Core and Builtins/2022-09-07-12-02-11.gh-issue-96636.YvN-K6.rst
Outdated
Show resolved
Hide resolved
|
Naive question: Do we expect this to have a performance impact, and should we measure it? |
|
Mark and I both benchmarked similar changes independently this week. I saw a 0% slowdown, he saw a 1% slowdown. So the perf impact is likely <1%. |
Co-authored-by: Brandt Bucher <brandtbucher@gmail.com>
…e-96636.YvN-K6.rst Co-authored-by: Brandt Bucher <brandtbucher@gmail.com>
Co-authored-by: Brandt Bucher <brandtbucher@gmail.com>
LGTM. The fix looks fine. Just one question about the tests.
|
Thanks @markshannon for the PR |
|
Sorry, @markshannon, I could not cleanly backport this to |
Co-authored-by: Brandt Bucher <brandtbucher@gmail.com> (cherry picked from commit aa3b4cf)
|
GH-96688 is a backport of this pull request to the 3.11 branch. |
NOTRACE_DISPATCHbreaks tracing #96636