multi-core-python
ideas
| multi-core-python | ideas | |
|---|---|---|
| 1 | 81 | |
| 237 | 1,651 | |
| - | 0.4% | |
| 10.0 | 7.3 | |
| over 1 year ago | 2 months ago | |
| BSD 3-clause "New" or "Revised" License | - |
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.
multi-core-python
-
Python 3.11 beta vs. 3.10 benchmark
At this point, I've given up hope that CPython will ever lose the GIL.
The best we can hope for is having multiple interpreters[0], each with their own GIL[1].
[0] https://peps.python.org/pep-0554/
[1] https://github.com/ericsnowcurrently/multi-core-python/issue...
ideas
-
Type information for faster Python C extensions
Lower latency native calls in Python would be extremely useful, thank you for your work! Is the following GitHub issue the right place to monitor progress? https://github.com/faster-cpython/ideas/issues/546
I'm open to doing some benchmarking. Several of my libraries have pure CPython bindings (StringZilla, UCall, SimSIMD), and all perform low-latency SIMD-accelerated ops, so might be a good testing ground :)
-
How Many Lines of C It Takes to Execute a and B in Python?
Recent CPython development has been towards optimizations and addressing use cases that benefit from optimizations, some coming from the faster CPython initiative. You might just get your JIT[1].
[1] https://github.com/faster-cpython/ideas/wiki/Workflow-for-3....
-
GIL removal and the Faster CPython project
The faster-cpython folks seem to be working towards a JIT (https://github.com/faster-cpython/ideas/tree/main/3.13) and both pyston and cinder have JITs. So I don't think anyone has ruled one out.
-
Our Plan for Python 3.13
faster-cpython team has done a lot of work to experiment on it: https://github.com/faster-cpython/ideas/issues/485#issuecomm...
It kind of sounds like migration to register based is a foregone conclusion, but it's not very clear to me.
-
Faster CPython at PyCon, part two
lots of big ideas are still remaining to be done. One example is the register based interpreter, see https://github.com/faster-cpython/ideas/issues/485
A previous plan called for the beginning of a JIT in 3.12, seen as "Trace optimized interpreter" here: https://github.com/faster-cpython/ideas/wiki/Workflow-for-3....
- EdgeDB – A graph-relational database built on top of Postgres
- Python 3.12 Nogil Benchmark
What are some alternatives?
python-speed - Simple Python Benchmark
Nuitka - Nuitka is a Python compiler written in Python. It's fully compatible with Python 2.6, 2.7, 3.4, 3.5, 3.6, 3.7, 3.8, 3.9, 3.10, and 3.11. You feed it your Python app, it does a lot of clever things, and spits out an executable or extension module.
faster-cpython - How to make CPython faster.
Pyjion - Pyjion - A JIT for Python based upon CoreCLR
pyenv-virtualenv - a pyenv plugin to manage virtualenv (a.k.a. python-virtualenv)
jnumpy - Writing Python C extensions in Julia within 5 minutes.
nogil - Multithreaded Python without the GIL
cinder - Cinder is Meta's internal performance-oriented production version of CPython.
hpy - HPy: a better API for Python
RustPython - A Python Interpreter written in Rust
LoopVectorization.jl - Macro(s) for vectorizing loops.
Tile38 - Real-time Geospatial and Geofencing