3 ms·
Benchmarks: http://uwsgi-docs.readthedocs.org/en/latest/PyPy_benchmarks.html http://uwsgi-docs.readthedocs.org/en/latest/PyPy_benchmarks.... Note that the benc
by fijal 13y ago
Benchmarks: http://uwsgi-docs.readthedocs.org/en/latest/PyPy_benchmarks.html http://uwsgi-docs.readthedocs.org/en/latest/PyPy_benchmarks....
Note that the benchmarks are preliminary as in there is both a lot of improvement possibility and we're not 100% sure if those are reasonable numbers. Also, the memory footprint mostly shows the base-interpreter size, your mileage may vary a lot.
- bsaul 13y agovery intersting link. the article mentions the possibility of pypy removing the GIL. Could anyone explain what's so difficult with GIL removal in general, and how,come pypy theoritically has this possibility while cpython does not ?
- fijal 13y agoGIL removal is easy. The hard part is that locking all the structures in order to avoid interpreter crashes (which are not acceptable in a language like python) is hard. It's not impossible though, jython did that. CPython additionally has a hard-to-remove refcounting GC strategy which makes it really hard to do any sort of GIL-less CPython without a major performance hit on locking every object at every refcount.
- jayflux 13y agohttp://pyvideo.org/video/1739/pypy-without-the-gil http://pyvideo.org/video/1739/pypy-without-the-gil here you go :)