[prev in list] [next in list] [prev in thread] [next in thread] 

List:       pypy-dev
Subject:    [pypy-dev] Saving and reloading JIT optimizations
From:       David Fraser <davidf () sjsoft ! com>
Date:       2011-08-19 11:56:43
Message-ID: 5d5c1b67-9bcd-4858-8d02-413db5acc17e () jackdaw ! local
[Download RAW message or body]

Hi

This is a fairly naive question from a newbie...

The pypy JIT takes a while to work out which parts of python code need optimization \
etc, and only after that phase do the speedups become relevant. Have there been any \
efforts (indeed, is it a feasible idea at all) that look at saving these \
                optimizations for future runs of the same codebase? The advantages \
                would be for:
 * Small programs that get run frequently - you could pre-tune the JIT but running a \
                longer batch and then save the results and take advantage of them \
                from startup
 * Application restarts not causing a slowdown (my case is a web application server - \
it would be nice if the first N page views weren't terribly slow as they are now)

Cheers
David

-- 
David Fraser
St James Software
_______________________________________________
pypy-dev mailing list
pypy-dev@python.org
http://mail.python.org/mailman/listinfo/pypy-dev


[prev in list] [next in list] [prev in thread] [next in thread]