Process-level fork on OpenJDK...is it madness?
Mark Roos
mroos at roos.com
Tue Nov 29 13:32:17 PST 2011
Interesting. I guess if you could save that state to disk and reload it
then you would have
the equivalent of the Smalltalk image concept. Although it seems like this
would be hard to
be op sys neutral.
It also seems it would help the warmup issue with Hotspot by preloadiing
its counters etc.
I just finished a paper (link below) on JVM startup time which states that
for small programs its around
70ms. So I assume there is some other startup time you are trying to
improve? Or is the
paper not applicable to the launching of a new process as you describe it?
I would think that someway to serialize application state would be more
interesting than an
complete clone of java memory and the following restart. As I recall from
the Smalltalk image
code the big issue was not the threads but was with all of the op sys
handles that need to
be reconstituted.
I look forward to the responses
mark
www.mii.lt/olympiads_in_informatics/pdf/INFOL073.pdf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.openjdk.java.net/pipermail/mlvm-dev/attachments/20111129/f63309a4/attachment.html
More information about the mlvm-dev
mailing list