@incubator.apache.org
Subject: Re: Introduction, and a question
My ambitions were far more modest, cutting down on startup overhead in
apps coded like this
static Foo aFoo = new Foo();
public void main(String args[])
{
checkpoint();
// on with the show
}
But JVM/instance persistence would
On Wed, May 18, 2005 at 10:40:41AM +0900, [EMAIL PROTECTED] wrote:
Newbie question: What is to stop us from caching JITed code? .NET/
mono does this as far as I know?
We can do it even in the forthcoming Harmony runtime.
On the other hand, an apparent drawback is disk
consumption.
5:45 AM
To: harmony-dev@incubator.apache.org
Subject: Re: Introduction, and a question
True, but if you saved the entire state of the JVM memory on disk (an
JVM 'hibernation'?) then you could just start from where you left,
instruction pointer included.
huuuh ...that would be awesome
Stefano Mazzocchi wrote:
Christian Damsgaard wrote:
I brought up this idea with Lars Bak (HotSpot architect at Sun back
then) at a conference some years back when Sun introduced the HotSpot
VM. The argument back then was that a program mays not execute in the
same pattern every time and the
-
From: Nick Lothian [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 17, 2005 10:36 AM
To: harmony-dev@incubator.apache.org
Subject: RE: Introduction, and a question
El lun, 16-05-2005 a las 16:08 +0530, Subramanian, Sundar escribió:
(...)
I guess what Brad is asking is for a snapshot
if any movement in this
direction is to be expected.
Regards
~sundar
-Original Message-
From: Nick Lothian [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 17, 2005 10:36 AM
To: harmony-dev@incubator.apache.org
Subject: RE: Introduction, and a question
El lun, 16-05-2005 a las 16
Newbie question: What is to stop us from caching JITed code? .NET/
mono does this as far as I know?
We can do it even in the forthcoming Harmony runtime.
On the other hand, an apparent drawback is disk
consumption. Generally, JITted native code takes 3 times or more as
much as bytecode takes.
I brought up this idea with Lars Bak (HotSpot architect at Sun back
then) at a conference some years back when Sun introduced the HotSpot
VM. The argument back then was that a program mays not execute in the
same pattern every time and the optimization made previously may no
longer apply.
