11 ms·
I love how easy this is to try out! I use pipenv, so I ran this: pipenv shell --python=python3.8 pip install pyston_lite_autoload And it worked: I go
by simonw 4y ago
I love how easy this is to try out!
I use pipenv, so I ran this:
pipenv shell --python=python3.8
pip install pyston_lite_autoload
And it worked: I got a small but material speed improvement from a tiny benchmark I ran against my own project: https://simonwillison.net/2022/Jun/8/pyston-lite/ https://simonwillison.net/2022/Jun/8/pyston-lite/
- drcongo 4y agoMy very unscientific test (just running the test suite on the Django project I happen to have up at the moment) proved to be very slightly slower with it installed: 11.2s - 11.3s without Pyston, 11.7s - 11.8s with Pyston.
- danuker 4y agoA test suite would be designed to call every routine in a project a limited number of times. This means the JIT compiler will be compiling each routine, for it to be run a few times then thrown away. Realistic loads might have the same routines run more intensely and might see more benefit from the JIT compiler.
- drcongo 4y agoAhhh, of course. Good point, thanks.
- kmod 4y agoAs someone else mentioned, test suites are a bit of a tough case for JITs. That said, we really don't want to slow down any workloads, and I suspect that something might be going wrong if you are getting a measurable slowdown. Is this project public? I'd love to investigate
- drcongo 4y agoIt's not, but after reading the other answer here I can totally see why it might be slightly slower. I'll definitely do some more testing with it beyond just timing my test suite runs.