pyinstrument VS snoop

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.

pdbpp: Improved pdb boltons: assorted python addtions twisted: event driven networking framework sorcery: Dark magic in python, things know where+how they are being called, helps reducing boilerplate sh: Better alternative for subprocess module, much more pythonic taskipy: npm run scipt_name like functionality snoop: pdb lite, record+replay function steps birdseye: graphical debugger remote-pdb: easy pdb from inside containers typer: wrapper around click for simpler code for CLIs arrow: Always TZ aware datetimes, plus more features more-itertools: more functions for iterators pydantic: data validation + dataclasses loguru: better logging notifiers: sending notifications from python

snoop or pysnooper

We have all used strategic print() statements in our code to make sure our code is running a certain line or to see the value of a variable. This gets a little sloppy and doesn't provide much context into why some code is not behaving as expected. Enter snoop, the super dead simple way to see exactly what the code is doing, the line of code that is executing, and when and what the values of local variables are. This can help us understand the flow of our code and identify issues much faster!

Try https://github.com/alexmojaki/snoop for both plus more.