-------- Original Message -------- Subject: Re: [Python-Dev] Python 3.3 vs. Python 2.7 benchmark results (again, but this time more solid numbers) Date: Sun, 28 Oct 2012 07:53:42 +1100 From: Tim Delaney <timothy.c.dela...@gmail.com> To: python-...@python.org On 28 October 2012 07:40, Mark Shannon <m...@hotpy.org <mailto:m...@hotpy.org>> wrote: I suspect that stating and loading the .pyc files is responsible for most of the overhead. PyRun starts up quite a lot faster thanks to embedding all the modules in the executable: http://www.egenix.com/__products/python/PyRun/ <http://www.egenix.com/products/python/PyRun/> Freezing all the core modules into the executable should reduce start up time. That suggests a test to me that the Cython guys might be interested in (or may well have performed in the past). How much of the stdlib could be compiled with Cython and used during the startup process? How much of an effect would it have on startup times and these benchmarks if Cython-compiled extensions were used? I'm thinking here of elimination of .pyc interpretation and execution (stat calls would be similar, probably slightly higher). To be clear - I'm *not* suggesting Cython become part of the required build toolchain. But *if* the Cython-compiled extensions prove to be significantly faster I'm thinking maybe it could become a semi-supported option (e.g. a HOWTO with the caveat "it worked on this particular system"). Tim Delaney
_______________________________________________ Python-Dev mailing list python-...@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/d.s.seljebotn%40astro.uio.no
_______________________________________________ cython-devel mailing list cython-devel@python.org http://mail.python.org/mailman/listinfo/cython-devel
