nogil
sbcl
nogil | sbcl | |
---|---|---|
31 | 59 | |
2,853 | 1,774 | |
- | 0.6% | |
5.7 | 9.9 | |
2 months ago | about 19 hours ago | |
Python | Common Lisp | |
GNU General Public License v3.0 or later | GNU General Public License v3.0 or later |
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/
sbcl
-
Arena Allocation in SBCL
Based on the commit message [0], and the references to "user code" in this document, my guess is that user programs have or will have access, but it's not finalized enough to be documented.
That being said, I suppose if you're developing an internal API for a compiler/interpreter, your "users" could be other parts of the project rather than language users.
https://github.com/sbcl/sbcl/commit/7f65522a16d857e41aa61cd0...
-
Steel Bank Common Lisp 2.3.8 released: “a mark-region parallel GC is available”
See for example:
https://github.com/sbcl/sbcl/blob/master/doc/internals-notes...
- Implementing Interactive Languages
-
Garbage Collection in a Large Lisp System (1984) [pdf]
related: the Immix inspired parallel-mark-region GC developed by Hayley Patton (https://github.com/no-defun-allowed/swcl) got merged recently into SBCL.
https://github.com/sbcl/sbcl/blob/master/doc/internals-notes...
https://applied-langua.ge/~hayley/swcl-gc.pdf
build with
./make.sh --without-gencgc --with-mark-region-gc (on x86-64/Linux and x86-64/macOS only at the moment).
-
SBCL: merge of mark-region GC
The Immix inspired mark-region GC developed by Hayley Patton (https://github.com/no-defun-allowed/swcl) got merged recently, which is pretty cool news for SBCL users.
- Owner of Symbolics Lisp machines IP is interested in a non-commercial release
- Steel Bank Common Lisp
What are some alternatives?
hpy - HPy: a better API for Python
ccl - Clozure Common Lisp
mypyc - Compile type annotated Python to fast C extensions
abcl - Armed Bear Common Lisp <git+https://github.com/armedbear/abcl/> <--> <svn+https://abcl.org/svn> Bridge
numpy - The fundamental package for scientific computing with Python.
sb-simd - A convenient SIMD interface for SBCL.
Pytorch - Tensors and Dynamic neural networks in Python with strong GPU acceleration
BQN - An APL-like programming language. Self-hosted!
python-feedstock - A conda-smithy repository for python.
cl-ppcre - Common Lisp regular expression library
cosmopolitan - build-once run-anywhere c library
maiko - Medley Interlisp virtual machine