bpo-45636: Simpler design for BINARY_OP/INPLACE_OP#29418
Conversation
|
Currently re-running benchmarks, for my own sanity… |
Sorry, something went wrong.
|
I'm glad I did. It seems that that single change contributes to the slowdown we saw on the other PR: DetailsIt's not clear to me why. Perhaps |
Sorry, something went wrong.
|
@brandtbucher Maybe the change created a branching point with random targets, so CPU branch predictor just gives up with prefetching. A profiler will help to find exact lines with the longest execution time. |
Sorry, something went wrong.
markshannon
left a comment
There was a problem hiding this comment.
I suspect the awkward size of nb_name_info may be responsible for most of the slowdown.
Sorry, something went wrong.
|
When you're done making the requested changes, leave the comment: |
Sorry, something went wrong.
|
You were right @markshannon: adjusting the alignment fixes the slowdown. Nice catch. Details |
Sorry, something went wrong.
No perf impact:
Details
https://bugs.python.org/issue45636