Skip to content
Closed
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Fix formatting of blurb
  • Loading branch information
mpage committed Apr 28, 2023
commit 975bd293ed3db6492dbbb3e80d23835f9953aa56
Original file line number Diff line number Diff line change
Expand Up @@ -2,10 +2,16 @@ When profiling an async Python application it's useful to see both the stack
for the currently executing task as well as the chain of coroutines that are
transitively awaiting the task. Consider the following example, where T
represents a task, C represents a coroutine, and A '->' B indicates A is
awaiting B.
awaiting B::

T0 +---> T1 | | | C0 | C2 | |
| v | v C1 | C3 | | +-----|
T0 +---> T1
| | |
C0 | C2
| | |
v | v
C1 | C3
| |
+-----|

The async stack from C3 would be C3, C2, C1, C0. In contrast, the
synchronous call stack while C3 is executing is only C3, C2. It's possible
Expand Down