4 ms·
Really nice tool to have in the toolbox, thanks for that. For the record I've installed Austin from AUR on Arch and austin-tui was not working (I've pinged the
by goffi 5y ago
Really nice tool to have in the toolbox, thanks for that. For the record I've installed Austin from AUR on Arch and austin-tui was not working (I've pinged the packager about that), and it was not working either with pypi version. It's working if I pipx install directly the git version though.
How does it play with async code?
- p403n1x87 5y agoThanks for reporting this. Do you mean an async tracee? Austin(p) handles all sorts of Python code, so should work with async like any other code.
- goffi 5y agoI've just realised after posting that the AUR package uses the git version, so it's actually normal that we have to use git version for austin-tui too and not the pypi one. Just if someone like me install the pypi version without paying attention, the git one is necessary. For async code, the issue with normal profiler is that we end up mostly in the event loop. In Python there is https://github.com/sumerc/yappi https://github.com/sumerc/yappi which has a notion of coroutine profiling (check the README there), so I'm wondering if this would make sense in the context of Austin. Anyway thanks for your work!
- p403n1x87 5y agoCheers! I have now released v1.0.0 of the TUI. The pip command requires an option to install pre-releases and that's why it was probably installing the old 0.2.0 version. As for the async profiles, I'd not expect the event loop own time to be on CPU, so using the -s option to collect only on-CPU samples should filter the event loop own time out.
- goffi 5y agoindeed the -s option helps, thanks for the tip.