wiwm i'd imagine it has a 3rd party tool. very nice to get it out of the box in 3.15

What I like about profiling.tracing is how you can control it in the same code base that you are profiling. That makes tracing into a feature you can ship, not just a tool you can attach. Profiling.sampling doesn't seem to provide anything similar, it has to run as a separate process

This sounds a lot like py-spy. How does it compare?

I'm not trying to criticize, but Python is known to be much slower than eg. Java or Go etc. So for performance-critcal code, why use Python? I find Python to be very good because it is concise and simple, but I have not used it for production so far.