NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
--Mark Hahn, <hahn@neurocog.lrdc.pitt.edu>
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Necessary but not Sufficient (Score:1)
JIT can help, if you have a tracing scheme (or a sufficiently simple language). One of the most important realizations is you must distinguish between heap and stack allocations [perl.org] -- making allocation as cheap as possible.
If you have a good tracing scheme, and if you can inline calls and branches cheaply, and if you have a parameter passing scheme which has as few memory copies as possible (go registers!), and if you have a sufficiently clever register allocation scheme which works across basic blocks, a JIT