3 ms·
For anyone curious, here's a set of benchmarks that compare Pyston vs PyPy (vs Python 3.11): https://www.phoronix.com/review/python311-pyston-pypy/2 https://ww
by mrtranscendence 4y ago
For anyone curious, here's a set of benchmarks that compare Pyston vs PyPy (vs Python 3.11):
https://www.phoronix.com/review/python311-pyston-pypy/2 https://www.phoronix.com/review/python311-pyston-pypy/2
They're neck and neck in most benchmarks, interestingly enough.
As to why not PyPy ... well, PyPy is a complete reimagining of how Python is implemented, so a merge would be infeasible. It would have to be a very disruptive transition and the appetite in the Python world for a big transition is ... minimal.
PyPy is also slower when calling into C extensions, so that's one downside. I'm not familiar enough with it to speak thoroughly, though.
- IanOzsvald 4y agoPyPy uses a modified Mark and Sweep garbage collector, CPython uses Reference Counting. C extensions such as NumPy (and so Pandas, sklearn etc) are compiled expecting Reference Counting. A translation layer is needed for memory management from PyPy to extensions like NumPy and that introduces overhead (historically - a lot of overhead).
- actionfromafar 4y agoSo, theoretically, all C extensions could be rewritten, too.