3 ms·
According to the promises of the Faster CPython Team, the JIT with a >50% speedup should have happened two years ago. Everyone knows Python is hard to optimize
by bgwalter 1y ago
According to the promises of the Faster CPython Team, the JIT with a >50% speedup should have happened two years ago.
Everyone knows Python is hard to optimize, that's why Mojo also gave up on generality. These claimed 20-30% speedups, apparently made by one of the chief liars who canceled Tim Peters, are not worth it. Please leave Python alone.
- deleted 1y ago[deleted]
- notatallshaw 1y agoTwo years ago was Python 3.11, my real world workloads did see a ~15-20% improvement in performance with that release. I don't remember the Faster CPython Team claiming JIT with a >50% speedup should have happened two years ago, can you provide a source? I do remember Mark Shannon proposed an aggressive timeline for improving performance, but I don't remember him attributing it to a JIT, and also the Faster CPython Team didn't exist when that was proposed. > apparently made by one of the chief liars who canceled Tim Peters Tim Peters still regularly posts on DPO so calling him "cancelled" is a choice: https://discuss.python.org/u/tim.one/activity https://discuss.python.org/u/tim.one/activity. Also, I really can not think who you would be referring to as part of the Faster CPython Team, of which all the former members I am aware of largely stayed out of the discussions on DPO.