poly-match
scalene
poly-match | scalene | |
---|---|---|
6 | 32 | |
31 | 11,191 | |
- | 1.6% | |
2.3 | 9.2 | |
28 days ago | 8 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.
poly-match
-
Improving Interoperability Between Rust and C++
Not my experience at all. At work we rewrote a small bit of hotspot python in Rust with no issues. This was what we primarily followed: https://ohadravid.github.io/posts/2023-03-rusty-python/
-
How to convince my boss that Rust is usable
Take at look at this example, it still uses Python as an interface to Rust code. Maybe you can do something similar to still achieve performance improvements without changing the entire codebase.
-
GDScript is fine
People are probably downvoting because it's needlessly hyperbolic and argumentative. Nobody is saying that python isn't faster to iterate with, but they're arguing that it would take months to get negligable performance gains in a lower level language, meanwhile here is a recent post from a company that increased the execution of they're python code by 100x with less than 100 lines of Rust. They also claim that nobody cares if something runs a few milliseconds faster, when we're talking about game dev, where games are frequently judged on how many milliseconds it takes to run game logic between frames.
-
Making Python 100x faster with less than 100 lines of Rust
Semi Vectorized code:
https://github.com/ohadravid/poly-match/blob/main/poly_match...
Expecting Python engineers unable to read defacto standard numpy code but meanwhile expect everyone can read Rust.....
Not to mention that the semi-vectorized code is still suboptimal. Too many for loops despite the author clearly know they can all be vectorized.
For example instead the author can just write something like:
np.argmin(
-
Blog Post: Making Python 100x faster with less than 100 lines of Rust
The article links to a full implementation, so you should be able to test this.
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)
- Scalene: A high-performance CPU GPU and memory profiler for Python
- Scalene: A high-performance, CPU, GPU, and memory profiler for Python
-
How can I find out why my python is so slow?
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.
https://github.com/plasma-umass/scalene
-
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.
-
Cum as putea sa imbunatatesc timpul de rulare al pitonului?
Ai vazut "Python Performance Matters" by Emery Berger (Strange Loop 2022)? E in principiu o prezentare si demo cu Scalene.
- Scalene - A Python CPU/GPU/memory profiler with optimization proposals
- Scalene: A Python CPU/GPU/memory profiler with optimization proposals
-
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
What are some alternatives?
jnumpy - Writing Python C extensions in Julia within 5 minutes.
flask-profiler - a flask profiler which watches endpoint calls and tries to make some analysis.
gopy - gopy generates a CPython extension module from a go package.
palanteer - Visual Python and C++ nanosecond profiler, logger, tests enabler
StaticCompiler.jl - Compiles Julia code to a standalone library (experimental)
pytest-austin - Python Performance Testing with Austin
truffleruby - A high performance implementation of the Ruby programming language, built on GraalVM.
memray - Memray is a memory profiler for Python
birthday-book-app - Rust in Anger: high-performance web applications
pyshader - Write modern GPU shaders in Python!
PythonCall.jl - Python and Julia in harmony.
viztracer - VizTracer is a low-overhead logging/debugging/profiling tool that can trace and visualize your python code execution.