[python_async_on_and_off_cpu] Add new check - #162
Open
KowalskiThomas wants to merge 1 commit into
Open
Conversation
KowalskiThomas
force-pushed
the
kowalski/python_async_on_and_off_cpu-add-new-check
branch
2 times, most recently
from
July 30, 2026 08:09
646782c to
8dbb2d8
Compare
KowalskiThomas
force-pushed
the
kowalski/python_async_on_and_off_cpu-add-new-check
branch
from
July 30, 2026 08:13
8dbb2d8 to
2fe634f
Compare
KowalskiThomas
marked this pull request as ready for review
July 30, 2026 08:13
gyuheon0h
reviewed
Jul 30, 2026
| @@ -0,0 +1,21 @@ | |||
| # python_async_on_and_off_cpu_3.11 | |||
|
|
|||
| _**Note** This workload currently does not behave as expected._ | |||
gyuheon0h
approved these changes
Jul 30, 2026
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.
What is this PR?
This PR adds a new correctness check where we have many off-CPU asyncio tasks and one on-CPU asyncio task.
In theory, we should see 100% of the CPU time attributed to the one on-CPU task and ~100% of the wall time attributed to the off CPU tasks (they're sleeping for much longer than the on-CPU task is computing for).
In practice, however, for now, due to the bias we know, ~100% CPU time is attributed to off-CPU tasks (which is clearly stated in the
README.md.This should get much better once we have timer-based profiling.