You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Can you reproduce the bug with PYTHONASYNCIODEBUG in env?: N/A
We're using uvloop in Tornado, and believe we may have an issue with too many pending tasks. Is it possible to monitor the number of tasks scheduled on uvloop and/or extract timing data for the tasks?
Further details: We discovered during a database slowdown that requests to unrelated parts of our application saw significantly increased latency (p50 approaching p99), which seems to indicate our async tasks were spending more of their time waiting to be scheduled rather than running. We'd like to validate this idea by recording any potential backup of tasks to be performed.
uvloop.Loop has a member _queued_streams which could be the sort of data we're looking for, but since that's in the Cython code we can't access it from Python.
The text was updated successfully, but these errors were encountered:
PYTHONASYNCIODEBUG
in env?: N/AWe're using uvloop in Tornado, and believe we may have an issue with too many pending tasks. Is it possible to monitor the number of tasks scheduled on uvloop and/or extract timing data for the tasks?
Further details: We discovered during a database slowdown that requests to unrelated parts of our application saw significantly increased latency (p50 approaching p99), which seems to indicate our async tasks were spending more of their time waiting to be scheduled rather than running. We'd like to validate this idea by recording any potential backup of tasks to be performed.
uvloop.Loop
has a member_queued_streams
which could be the sort of data we're looking for, but since that's in the Cython code we can't access it from Python.The text was updated successfully, but these errors were encountered: