[pypy-dev] JIT for scripts
fijall at gmail.com
Wed Jun 1 15:03:57 CEST 2011
On Wed, Jun 1, 2011 at 2:14 PM, Alex Şuhan <alex.suhan at gmail.com> wrote:
> PyPy works great for our PHP JIT interpreter, with nice speedups for most of
> the processing-intensive (with loops), shootout-ish scripts. However, I feel
> that short scripts running often could benefit from tracing as well if we
> make the interpreter „persistent” -- that is, keep all the scripts in
> memory, create a jump (with a variable target) for dispatching the requested
> script and a backward jump (to the fore-mentioned dispatch jump) at the end
> of each script. This article:
> refers to the loop_longevity JIT parameter, which suggests it's possible to
> have alternative executions between different scripts and PyPy will simply
> pick the appropriate trace as long as it's not too old.
Hi, that's great to hear!
Can you think about keeping stuff somehow in-process (I think
mod_python and mod_wsgi do some tricks along these lines for example)
instead of starting new process for each script? That requires a need
of cleaning up global state, but you'll get jit compiled assembler
staying in memory.
PS. I might not be understanding what are your proposed solution
> Other than the obvious duct taping, are there any caveats to this solution?
> pypy-dev mailing list
> pypy-dev at python.org
More information about the pypy-dev