4 ms·
Benchmarks aren't too promising[0]. I wonder if the original 500% improvement they targeted at the start of the `faster cpython` project is still a realistic t
by vb-8448 3y ago
Benchmarks aren't too promising[0].
I wonder if the original 500% improvement they targeted at the start of the `faster cpython` project is still a realistic target.
[0] https://github.com/faster-cpython/benchmarking-public https://github.com/faster-cpython/benchmarking-public
- Varriount 3y agoWould those benchmarks capture the performance improvements listed in the change log? From what I read, there were two big ones: - Inlined list and set comprehensions. - Reduced data copying in asyncio.
- vb-8448 3y agoThey use the `pyperformance` package[0] that, according to the readme, use real world scenarios. So I expect it to capture every significant improvement. [0]https://github.com/python/pyperformance https://github.com/python/pyperformance
- notatallshaw 3y agoMy understanding is most low hanging fruit were picked for Python 3.11. And the faster CPython team have been looking at more mid to long term goals with the addition of a JIT and other accompanying infrastructure around for 3.13 and 3.14. However, the recent no-GIL decision I think has sent a few things back to the drawing board to see what can and cannot be salvaged from their progress and plans so far.
- vb-8448 3y agoSad ... I think python need some performance improvement more than the no-gil stuff.