GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | ||||||||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | ||||||||
GeezerVison is showing github.com — gh-128588: gh-128550: remove eager tasks optimization that missed and introduced incorrect cancellations by graingert · Pull Request #129063 · python/cpython Conversation
|
|
Thanks @graingert for the PR, and @kumaraditya303 for merging it 🌮🎉.. I'm working now to backport this PR to: 3.12, 3.13. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
…t missed and introduced incorrect cancellations (pythonGH-129063) (cherry picked from commit ed6934e) Co-authored-by: Thomas Grainger <[email protected]> Co-authored-by: Kumar Aditya <[email protected]>
|
Sorry, @graingert and @kumaraditya303, I could not cleanly backport this to |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
GH-129089 is a backport of this pull request to the 3.13 branch. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
…sed and introduced incorrect cancellations (GH-129063) (#129089) gh-128588: gh-128550: remove eager tasks optimization that missed and introduced incorrect cancellations (GH-129063) (cherry picked from commit ed6934e) Co-authored-by: Thomas Grainger <[email protected]> Co-authored-by: Kumar Aditya <[email protected]>
…t missed and introduced incorrect cancellations (python#129063) Co-authored-by: Kumar Aditya <[email protected]>
|
What's the impact of removing this optimization on the async_tree pyperformance benchmarks? |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
I haven't benchmarked yet, I'll do it but I expect an insignificant impact. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
…er tasks optimization that missed and introduced incorrect cancellations (#129063) (#128586) Co-authored-by: Kumar Aditya <[email protected]>
…t missed and introduced incorrect cancellations (python#129063) Co-authored-by: Kumar Aditya <[email protected]>
any update on benchmarking results @kumaraditya303 ? benchmarking of the original PR showed up to 4x speedup on some of the async benchmarks. anything changed that you expect removing the optimization would have insignificant impact? |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
I had asked Michael to benchmark this last week but I haven't heard back from them, I'll ping them again but meanwhile I compared the rough number by comparing benchmarks with and without this patch and I don't see any large slowdown on the benchmarks: With this PR: |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Hmm, I think I see what's going on here.. Looking more closely at the original PR, it appears the benchmarking used a patched version of pyperformance to add an "eager" flavor to the async tree benchmarks. Since these flavors don't exist in the released version of pyperformance, we don't see them in the benchmark runs... |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
There was an error while loading. Please reload this page.