py-spy VS pyinstrument

For CPU cycles, py-spy[0] is getting more and more used. For RAM, I would like to known too...

[0] -- https://github.com/benfred/py-spy

Theres also Py Spy, a profiling tool that can generate flame charts containing a mix of python and C (or C++) calls.

https://github.com/benfred/py-spy

It's worked really well for my needs

You should profile your consumer to check the bottlenecks. You can use the excellent py-spy(written in Rust). IMO a few usage of Numba there and there should solve your performance issues.

So as a first step you'll want to profile your program to figure out where it's slow, and hopefully that'll also tell you why it's slow. I'm the (biased) author of the Sciagraph profiler which is designed for this sort of application (https://sciagraph.com) but you can also try py-spy, which isn't as well designed for data processing/analysis applications (e.g. it won't visualize parallelism at all) but can still be informative (https://github.com/benfred/py-spy). Both are written in Rust ;)

Any advantages/disadvantages compared to py-spy [1]?

[1]: https://github.com/benfred/py-spy

Python profiling is enabled primarily through cprofile, and can be visualized with help of tools like snakeviz (output flame graph can look like this). There are also memory profilers like memray which does in-depth traces, or sampling profilers like py-spy.

A good profiler would be https://github.com/benfred/py-spy . If you run your app/benchmark with it, it should be able to draw a flamegraph telling you where the majority of time is spent. The info here is quite fine grained so it would already tell you where the bottleneck is. Without a full-fledged profiler you can also measure the timings in various parts of the code to understand where the bottleneck is.

Might be worth raising an issue on py-spy (a python profiler written in rust which "supports profiling native python extensions written in languages like C/C++ or Cython" to see if that can close the loop.

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.