austin
mpb
Our great sponsors
austin | mpb | |
---|---|---|
12 | 3 | |
1,346 | 2,209 | |
- | - | |
7.5 | 8.8 | |
12 days ago | about 9 hours ago | |
C | Go | |
GNU General Public License v3.0 only | The Unlicense |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
austin
-
Memray – A Memory Profiler for Python
I collected a list of profilers (also memory profilers, also specifically for Python) here: https://github.com/albertz/wiki/blob/master/profiling.md
Currently I actually need a Python memory profiler, because I want to figure out whether there is some memory leak in my application (PyTorch based training script), and where exactly (in this case, it's not a problem of GPU memory, but CPU memory).
I tried Scalene (https://github.com/plasma-umass/scalene), which seems to be powerful, but somehow the output it gives me is not useful at all? It doesn't really give me a flamegraph, or a list of the top lines with memory allocations, but instead it gives me a listing of all source code lines, and prints some (very sparse) information on each line. So I need to search through that listing now by hand to find the spots? Maybe I just don't know how to use it properly.
I tried Memray, but first ran into an issue (https://github.com/bloomberg/memray/issues/212), but after using some workaround, it worked now. I get a flamegraph out, but it doesn't really seem accurate? After a while, there don't seem to be any new memory allocations at all anymore, and I don't quite trust that this is correct.
There is also Austin (https://github.com/P403n1x87/austin), which I also wanted to try (have not yet).
Somehow this experience so far was very disappointing.
(Side node, I debugged some very strange memory allocation behavior of Python before, where all local variables were kept around after an exception, even though I made sure there is no reference anymore to the exception object, to the traceback, etc, and I even called frame.clear() for all frames to really clear it. It turns out, frame.f_locals will create another copy of all the local variables, and the exception object and all the locals in the other frame still stay alive until you access frame.f_locals again. At that point, it will sync the f_locals again with the real (fast) locals, and then it can finally free everything. It was quite annoying to find the source of this problem and to find workarounds for it. https://github.com/python/cpython/issues/113939)
- Pystack: Like Pstack but for Python
- High performance profiling for Python 3.11
-
tqdm (Python)
Just wanted to add Austin: Python frame stack sampler for CPython written in pure C (https://github.com/P403n1x87/austin)
- Pyheatmagic: Profile and view your Python code as a heat map
-
Spy on Python down to the Linux kernel level
If you follow the call stack carefully you should be able to get to the point where sklearn calls ddot_kernel_8 (indirectly in this case). Austin(p) reports source files as well, so that shouldn't be a problem (provided all the debug symbols are available). If you're collecting data with austinp, don't forget to resolve symbol names with the resolve.py utility (https://github.com/P403n1x87/austin/blob/devel/utils/resolve..., see the README for more details: https://github.com/P403n1x87/austin/blob/devel/utils/resolve...)
- (How to) profile python code?
- Austin – Python Frame Stack Sampler (or zero-instrumentation profiling) 2.1.1
mpb
-
Looking for a package that can show multi-lined, multiple progress bar
You might suggest using mpb but I don't think mpb would fit my desire, because it is mainly for 'one line for one progress bar'.
- Create multi-line loading bars?
-
tqdm (Python)
While not having all the tqdm features, i find mpb to be quite good actually.
What are some alternatives?
go-isatty
uiprogress - A go library to render progress bars in terminal applications
chalk - Intuitive package for prettifying terminal/console output. http://godoc.org/github.com/ttacon/chalk
frep - Generate file using template from environment, arguments, json/yaml/toml config files
termui - Golang terminal dashboard
termenv - Advanced ANSI style & color support for your terminal applications
uitable - A go library to improve readability in terminal apps using tabular data
pterm - ✨ #PTerm is a modern Go module to easily beautify console output. Featuring charts, progressbars, tables, trees, text input, select menus and much more 🚀 It's completely configurable and 100% cross-platform compatible.
clui - Command Line User Interface (Console UI inspired by TurboVision)
pyinstrument - 🚴 Call stack profiler for Python. Shows you why your code is slow!
aurora - Golang ultimate ANSI-colors that supports Printf/Sprintf methods
go-colorable