Am 17.02.2011 17:19, schrieb Alessio Stalla: [...]
I agree, and I'd like to add that memory mapping the classes is only a partial solution; the optimum would be to also save live object instances (perhaps starting from selected roots), since I suspect that for many languages a significant part of the loading time is spent establishing the initial state of the language runtime (at least this is true for ABCL [1]).
it is the same for Groovy. Even though I think the startup time for Groovy is not too bad, it is still at least Java doubled and that is for many things just too slow.
> Doing this in general is not easy at all (what
about open file descriptors, running threads, and all similarly non-persistent resources?), and I don't see compelling reasons for Oracle to embark in such an effort (given that the JVM is prevalently used in server environments where cold restarts are rare). Still, save-image is supported by all major Lisp implementations (and Smalltalk, I believe), and used to minimize startup times and deliver self-contained executables.
I wonder what exactly would have to be done to enable that for the OpenJDK bye Jochen -- Jochen "blackdrag" Theodorou The Groovy Project Tech Lead http://blackdragsview.blogspot.com/ For Groovy programming sources visit http://groovy.codehaus.org -- You received this message because you are subscribed to the Google Groups "JVM Languages" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/jvm-languages?hl=en.
