11–20 of 44 posts
"top" for python programs. Thats pretty awesome - not sure if this has existed in other traces, but the output is great.
Imagine it should also provide relevant insights into the structure of this tool
TAU: https://www.cs.uoregon.edu/research/tau/docs/newguide/ch03s0... Extrae/Paraver: https://www.researchgate.net/publication/317485375_Performan... llel_Python_Applications Score-p/Scalasca: http://score-p.org https://github.com/score-p/scorep_binding_python
Does it support python multiprocessing? Basically nothing out there does that I've found, and it's a really major pain-point for me.
"top" for python programs. Thats pretty awesome - not sure if this has existed in other traces, but the output is great.
If you're talking about the flame graphs, they're a fairly common feature of modern profilers. The oldest implementation I know of is at https://github.com/brendangregg/FlameGraph .
Earlier quoted context omitted.
If you're talking about the flame graphs, they're a fairly common feature of modern profilers. The oldest implementation I know of is at https://github.com/brendangregg/FlameGraph .
I've never understood why flame graphs are better than the normal presentation of inclusive and exclusive timings in performance tools, even if they're not "modern", but embody some decades' experience. Anyone care to explain?
It shows the call paths to the functions and what part each path took, that's not so obvious from the typical table. On the other hand, finding functions that are called quite a lot all over the place and add up is easier in the table, so it's not become useless.
Wonderful. Can the data it produces be munged into something KCachegrind can show?
Many thanks for building and releasing this. It's ridiculously easy to install (especially in virtualenvs) and very powerful. When I push '3' or '4', I get informative, stable output. Minor feature request: an explicit 'pause' button would make it easier to copy file paths from the output. Ctrl-S is a reasonable alternative, but it's a little hacky. Also, it would be nice to somehow eliminate time spent in poll() fro…
"top" for python programs. Thats pretty awesome - not sure if this has existed in other traces, but the output is great.
If you're talking about the flame graphs, they're a fairly common feature of modern profilers. The oldest implementation I know of is at https://github.com/brendangregg/FlameGraph .
Does it support python multiprocessing? Basically nothing out there does that I've found, and it's a really major pain-point for me.
yappi? https://bitbucket.org/sumerc/yappi/
It basically boils down to (currently) doing multiprocessing profiling is a giant pain in the ass, you have to manually attach the profiler yourself if you ever launch another process, and every profiled process produces it's own output file.
It's not impossible, it's just very annoying. I've been vaguely meaning to write a thing which attaches to the fork() call and automatically starts the profiler in the child-process, and handles aggregating all the results back to a single output when all children exit.