Hi Mark, This sounds really cool. Can you give us more details? Some questions that occurred to me while reading: - You're suggesting that the contractor would only be paid if the desired 50% speedup is achieved, so I guess we'd need some objective Python benchmark that boils down to a single speedup number. Did you have something in mind for this? - How much of the work has already been completed? - Do you have any preliminary results of applying that work to that benchmark? Even if it's preliminary, it would still help a lot in making the case for this being a realistic plan. -n On Tue, Oct 20, 2020 at 6:00 AM Mark Shannon <mark@hotpy.org> wrote:
Hi everyone,
CPython is slow. We all know that, yet little is done to fix it.
I'd like to change that. I have a plan to speed up CPython by a factor of five over the next few years. But it needs funding.
I am aware that there have been several promised speed ups in the past that have failed. You might wonder why this is different.
Here are three reasons: 1. I already have working code for the first stage. 2. I'm not promising a silver bullet. I recognize that this is a substantial amount of work and needs funding. 3. I have extensive experience in VM implementation, not to mention a PhD in the subject.
My ideas for possible funding, as well as the actual plan of development, can be found here:
https://github.com/markshannon/faster-cpython
I'd love to hear your thoughts on this.
Cheers, Mark. _______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-leave@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/RDXLCH22... Code of Conduct: http://python.org/psf/codeofconduct/
-- Nathaniel J. Smith -- https://vorpus.org <http://vorpus.org>