yappi VS pyinstrument

yappi

I'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 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!

I was wondering if you have any synchronous routes in your app? We have an open issue regarding those and would love some ideas for solutions :)

Is there something about the actual profiler that differs from existing tools like pyinstrument [1] or py-spy [2]? I know pyinstrument has various output options and I wonder if it could potentially output something readable by the Firefox Profiler tool.

[1] : https://github.com/joerick/pyinstrument

I would highly recommend looking into pyinstrument to profile your requests. I find the reports to be very readable, and it's very easy to setup with Django.

I like to use pyinstrument for profiling. Uses stat sampling so it's quicker and builds a easy to grok report.

Hello! I just released pyinstrument 4.0 on PyPI. pyinstrument was my first successful open-source package and I love seeing how much use it's getting in the community.

PyInstrument, compared to cProfile or Yappi, it's a lot easier to use and requires much less configuration.

Run pytest, under pyinstrument, and generate a webpage that presents performance data, in addition to a separate junit xml report.