It is certainly an enticing idea. JIT compilation offers even more code optimisation than conventional pre-compilation so it would be quite interesting what would happen if someone did write a jvm with jit and an executable caching scheme. The jvm would jit-compile the code and save the results to be reused and ideally even profile the code even more with subsequent runs (if required). There is an interesting article about HP Dynamo project I remember that dealt with jit performance performance benefits: http://www.arstechnica.com/reviews/1q00/dynamo/dynamo-1.html
However the code size would grow dramatically, for every java class there would be an executable cache which would probably more than double the effective size of the class takes up on disk. "Larry Meadors" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > Are there any JITs that save what they do? > > What I mean is instead of compiling into memory and losing the work when > the jvm exits, compiling to disk and reusing the compiled code later? > > That would be a killer tool. > > Larry > > > ---------------------------------------------------------------------- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > ---------------------------------------------------------------------- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
