[summerofcode] idea of speedup interpreter startup

Linan Wang tali.wang at gmail.com
Mon Jun 6 02:33:19 CEST 2005


hi, everybody,

Let's go to the topic directly :)
I propose to use "lazy import" strategy to handle modula import. 
The term lazy here means import the compiled function's code only
before first using it. Sometimes we only use few functions/classes in
a module, but it seems we import all the compiled code when we do
importing. It's quite a waste of time and resource.
By introducing a function/class table at some place of compiled code,
we can import only the definition of the module. When before firing a
function in a module, interpreter does the real import action.

This idea maybe considered before and abandoned because of  the cost
of IO operation, rr, the implementation of lazy strategy for classes
import is a quite complex.

Does this idea make sense? Any mentors want to give me some ideas?
Thanks alot!

-- 
Wang
-----------------------------------------------
Email:tali.wang at gmail.com
Or: arp04lw at shef.ac.uk
-----------------------------------------------


More information about the summerofcode mailing list