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
and got the following graph, and all it seems to show is hundreds of threads that spend their time in /usr/local/lib/python3.12/threading.py:Condition.wait:359.
When I try to run with austin -e -i 10ms -x 120 -p 10 -o sample.out, it says
😣 No samples collected.
For comparison, the output of py-spy which properly shows the asyncio run's loop and where it actually spends its time:
The text was updated successfully, but these errors were encountered:
@ScientiaEtVeritas thanks for reporting this. Austin doesn't have a proper async support. One thing you could try is the -s option to collect only the samples that are on CPU
austin -si 20ms -x 120 -p 8 -o sample.out
For better async profiling in general, you could try echion instead.
I ran
austin -i 20ms -x 120 -p 8 -o sample.out
and got the following graph, and all it seems to show is hundreds of threads that spend their time in /usr/local/lib/python3.12/threading.py:Condition.wait:359.
When I try to run with
austin -e -i 10ms -x 120 -p 10 -o sample.out
, it saysFor comparison, the output of py-spy which properly shows the asyncio run's loop and where it actually spends its time:
The text was updated successfully, but these errors were encountered: