nogil
rayon
nogil | rayon | |
---|---|---|
31 | 67 | |
2,854 | 10,277 | |
- | 1.9% | |
5.7 | 9.0 | |
2 months ago | 12 days ago | |
Python | Rust | |
GNU General Public License v3.0 or later | 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.
nogil
- Proof-of-Concept Multithreaded Python Without the GIL
-
Our Plan for Python 3.13
This might be a dumb question, but why would removing the GIL break FFI? Is it just that existing no-GIL implementations/proposals have discarded/ignored it, or is there a fundamental requirement, e.g. C programs unavoidably interact directly with the GIL? I know that the C-API is only stable between minor releases [0] compiled in the same manner [1], so it's not like the ecosystem is dependent upon it never changing.
I cannot seem to find much discussion about this. I have found a no-GIL interpreter that works with numpy, scikit, etc. [2][3] so it doesn't seem to be a hard limit. (That said, it was not stated if that particular no-GIL implementation requires specially built versions of C-API libs or if it's a drop-in replacement.)
[0]: https://docs.python.org/3/c-api/stable.html#c-api-stability
[1]: https://docs.python.org/3/c-api/stable.html#platform-conside...
[2]: https://github.com/colesbury/nogil
[3]: https://discuss.python.org/t/pep-703-making-the-global-inter...
-
Real Multithreading Is Coming to Python
https://github.com/colesbury/nogil does manage to get rid of the GIL, but it's not certain to make it into Python core. The main problem is the amount of existing libraries that depend on the existence of the GIL without realizing it - breaking those would be extremely disruptive.
-
[D] The hype around Mojo lang
CPython is also investigating the removal of the GIL (PEP703, nogil). I think requiring the GIL is a wider thing that libraries will need to address anyway. But also, for the same reason as above I'd be surprised if the Modular team thought that saying "you can run all your python code unchanged" was a good idea if there was a secret "except for code that uses numpy" muttered under the breath.
- PEP 684 was accepted – Per-interpreter GIL in Python 3.12
- PEP 703 – Making the Global Interpreter Lock Optional in CPython
-
Python 3.11.0 final is now available
I'm worried about the speedup
My understanding is that it's based on the most recent attempt to remove the GIL by Sam Gross
https://github.com/colesbury/nogil
In addition to some ways to try to not have nogil have as much overhead he added a lot of unrelated speed improvements so that python without the gil would still be faster not slower in single thread mode. They seem to have merged those performance patches first that means if they add his Gil removal patches in say python 3.12 it will still be substantially slower then 3.11 although faster then 3.10. I hope that doesn't stop them from removing the gil (at least by default)
- Removed the GIL back in 1996 from Python 1.4, primarily to create a re-entrant Python interpreter.
- I Tried Removing Python's GIL Back in 1996
-
Faster CPython 3.12 Plan
Looks like it's still active to me:
https://github.com/colesbury/nogil/
rayon
- Rayon: Data-race free parallelization of sequential computations in Rust
- Too Dangerous for C++
-
Which application/problem would you choose for presenting Rust to newcomers in 1h30min?
Do some operations with .iter() then later use rayon to parallelize. So you can show how easy is to add a dependency and how easy is to parallelize.
-
What Are The Rust Crates You Use In Almost Every Project That They Are Practically An Extension of The Standard Library?
rayon: Async CPU runtime for parallelism.
-
Moving from Typescript and Langchain to Rust and Loops
In the quest for more efficient solutions, the ONNX runtime emerged as a beacon of performance. The decision to transition from Typescript to Rust was an unconventional yet pivotal one. Driven by Rust's robust parallel processing capabilities using Rayon and seamless integration with ONNX through the ort crate, Repo-Query unlocked a realm of unparalleled efficiency. The result? A transformation from sluggish processing to, I have to say it, blazing-fast performance.
-
AreWeMegafactoryYet? I just breached simulating 1M buildings @ 60 fps (If I'm not recording, Ryzen 7 1700X 8 Core)
With a lot of rayon, blood, sweat and tears I finally managed to simulate a million buildings at 60fps :) Feel free to AMA, game is Combine And Conquer
-
The Rust I Wanted Had No Future
(see https://github.com/rayon-rs/rayon/tree/master/src/iter/plumbing)
-
Parallel event iterator?
I did some very basic testing with this crate : https://crates.io/crates/rayon and it seems to work :
-
General Recommendations: Should I Use Tree-sitter as the AST for the LSP I am developing?
Sequentially, generating tree-sitter AST for each file and querying for the links of each file takes around 2.3 seconds. However, I randomly remembered this crate rayon, and I decided to test it. It ended up improving the performance (just by changing 2 lines of code) to 200-300ms by parallelizing the iterators and tree-sitter queries. MAJOR.
-
python to rust migration
Now if you really want to use Rust, you can rewrite only the part that are slowing down your consumer. It's easy by using Py03 and maturin. Maybe also rayon to parallelize.
What are some alternatives?
hpy - HPy: a better API for Python
crossbeam - Tools for concurrent programming in Rust
mypyc - Compile type annotated Python to fast C extensions
tokio - A runtime for writing reliable asynchronous applications with Rust. Provides I/O, networking, scheduling, timers, ...
numpy - The fundamental package for scientific computing with Python.
RxRust - The Reactive Extensions for the Rust Programming Language
Pytorch - Tensors and Dynamic neural networks in Python with strong GPU acceleration
rust-numpy - PyO3-based Rust bindings of the NumPy C-API
python-feedstock - A conda-smithy repository for python.
tokio-rayon - Mix async code with CPU-heavy thread pools using Tokio + Rayon
sbcl - Mirror of Steel Bank Common Lisp (SBCL)'s official repository
coroutine-rs - Coroutine Library in Rust