4 ms·
the JIT compiler is itself automatically generated Indeed it is. Compiling took 9000s on a 2GHz Dual Core Athlon with 2GB RAM. Don't even try to compile it on
by johkra 16y ago
the JIT compiler is itself automatically generated
Indeed it is. Compiling took 9000s on a 2GHz Dual Core Athlon with 2GB RAM. Don't even try to compile it on a machine with 1GB RAM, your system will start trashing heavily and finish sometimes between next week and never. </rant>
But after downloading the binaries, I have to say: Wow! One of my naive project euler solution is about 3-4 times faster than it was using Psyco. Absolutely impressive. (Numbers: ~66s Python 2.6, ~8.6s Psyco, ~2.8s PyPy)
- ulrich 16y agoThat sounds great. Does it have any drawbacks like a high startup time?
- rbanffy 16y agoLast time I checked, PyPy was not compatible with modules written in C for CPython. IIRC, they wanted to correct that.
- masterj 16y agoI believe they have alpha support now, but it's still very buggy.
- johkra 16y agoI just tried it. On first start up (when the 13MB pypy executable has to be loaded into memory), it's slightly slower. About 0.5 to 1.0 seconds, I'd guess. My highly scientific benchmarks (time python -c "pass") give no noticeable difference, with pypy starting in between 0.015s and 0.020s and Python 2.6 starting in 0.022s to 0.028s. All of this is on a 1.6GHz C2D, 1GB RAM, Arch Linux 32 bit.
- stcredzero 16y ago13MB? Seems like a lot. I think the full IDE, plus version control and all base libraries fits into a 14MB VisualWorks Smalltalk image. (Plus, if you disabled the splash screen and herald WAV, it would start faster than Perl 5.) Executable used to be way smaller than 1MB.