scalene
coveragepy
Our great sponsors
scalene | coveragepy | |
---|---|---|
32 | 7 | |
11,015 | 2,796 | |
2.0% | - | |
9.3 | 9.6 | |
4 days ago | 6 days ago | |
Python | Python | |
Apache License 2.0 | Apache License 2.0 |
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.
scalene
-
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)
-
How can I find out why my python is so slow?
Try using scalene to find where your code is running slow (and/or consuming lots of memory). You're talking two different OSs here, there are a ton of things that could explain the difference. But profiling will help you find where the bottleneck is
Use this my fren: https://github.com/plasma-umass/scalene
-
Making Python 100x faster with less than 100 lines of Rust
You should take a look at Scalene - it's even better.
-
Blog Post: Making Python 100x faster with less than 100 lines of Rust
I like seeing another Python profiler. The one I've been playing with is Scalene (GitHub). It does some fun things related to letting you see how much things are moving across the system Python memory boundary.
-
OpenAI might be training its AI technology to replace some software engineers, report says
I tried out some features of machine learning models suggesting optimisations on code profiled by scalene and pretty much all of them would make the code less efficient, both time and memory wise. I am not worried. The devil is in the details and ML will not replace all of us anytime soon
- Modules Import and Optimisation
-
[2022 day 16 (part 2)] [python 3.10] Can my solution be optimized?
Can't say about the floyd-warshall, since that's from elsewhere. However, I'd suggest profiling the code. For example scalene is pretty decent python profiler.
-
What are some features you wish Python had?
How about scalene?
-
Dwarf-Based Stack Walking Using eBPF
This is super awesome work and a great technical explanation of a very deep topic.
What happens in the case of JIT or FFI? I think I've only ever seen the Python profiler, scalene[0], handle these cases.
coveragepy
-
An Introduction to Testing with Django for Python
Coverage.py is the go-to tool for measuring code coverage of Python programs. Once installed, you can use it with either unittest or pytest.
-
The Uncreative Software Engineer's Compendium to Testing
Code Coverage Analysis assess the code portions tested by the current test suites without altering the code.
-
Slipcover: Near Zero-Overhead Python Code Coverage
The PLASMA lab @ UMass Amherst (home of the Scalene profiler) has released a new version of Slipcover, a super fast code coverage tool for Python. It is by far the fastest code coverage tool: in our tests, its average slowdown is just 5% (compare to the widely used coverage.py, average slowdown 218%!). The latest release performs both line and branch coverage with virtually no overhead. Use it to dramatically speed up your tests and continuous integration!
-
Unit Tests - what’s the point?
Tests ensure the tested behavior is maintained. It's up to the developers to write tests with sufficient coverage. Determining which lines of code on your project are covered by tests is easily quantifiable using tooling. E.g. https://coverage.readthedocs.io/
-
How to make Django package smaller for Serverless deployment
Taking the idea further, if you build robust tests for your API, you could use a dynamic code analyzer like coverage or figleaf to identify and delete unused functions.
-
Comparison of Python TOML parser libraries
coverage
-
New Ways to Be Told That Your Python Code Is Bad
FWIW, ternary expressions aren't properly detected by coverage: https://github.com/nedbat/coveragepy/issues/509
What are some alternatives?
flask-profiler - a flask profiler which watches endpoint calls and tries to make some analysis.
palanteer - Visual Python and C++ nanosecond profiler, logger, tests enabler
pytest-austin - Python Performance Testing with Austin
memray - Memray is a memory profiler for Python
pyshader - Write modern GPU shaders in Python!
viztracer - VizTracer is a low-overhead logging/debugging/profiling tool that can trace and visualize your python code execution.
Dask - Parallel computing with task scheduling
Keras - Deep Learning for humans
magic-trace - magic-trace collects and displays high-resolution traces of what a process is doing
dask-memusage - A low-impact profiler to figure out how much memory each task in Dask is using
dtale - Visualizer for pandas data structures
NumPy - The fundamental package for scientific computing with Python.