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
When running profiler, it will show a request as the cumulative of all tasks - even ones run in the background. When looking at actual latency of the request, it will accurately represent the time. This is using the profiler as:
Actual measured latency: 0.321
Wall clock time should not include the background task total time since we are not awaiting it. I understand that pyinstrument follows the async context, but it doesn't seem like it is properly measuring the event loop itself.
The text was updated successfully, but these errors were encountered:
When running profiler, it will show a request as the cumulative of all tasks - even ones run in the background. When looking at actual latency of the request, it will accurately represent the time. This is using the profiler as:
The output will look like:
Actual measured latency: 0.321
Wall clock time should not include the background task total time since we are not awaiting it. I understand that pyinstrument follows the async context, but it doesn't seem like it is properly measuring the event loop itself.
The text was updated successfully, but these errors were encountered: