You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@harmony.apache.org by Weldon Washburn <we...@gmail.com> on 2006/06/02 08:02:27 UTC
{DRLVM] MMTK bootstrap design issues
All,
The conventional approach is to ahead of time compile MMTK to an
executable image. Then load this image during JVM initialization.
This means building some sort of AOT infrastructure. I would like to
avoid this for initial bring up if at all possible. Instead, I am
thinking of forcing Jitrino.JET to jit all MMTK classes during JVM
bootstrap. My guess is that this will slow down bootup by 1-2
seconds. In other words, no biggie because we can always go back and
clean this up once some else installs AOT infrastructure.
One gotcha is that there can be no real garbage collection before MMTK
has been JITed. Its not likely to be a big problem since
bootstrapping a JVM does not burn up gigabytes of java heap.
Thoughts?
--
Weldon Washburn
Intel Middleware Products Division
---------------------------------------------------------------------
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: harmony-dev-unsubscribe@incubator.apache.org
For additional commands, e-mail: harmony-dev-help@incubator.apache.org
Re: {DRLVM] MMTK bootstrap design issues
Posted by Rodrigo Kumpera <ku...@gmail.com>.
On 6/2/06, Weldon Washburn <we...@gmail.com> wrote:
> All,
>
> The conventional approach is to ahead of time compile MMTK to an
> executable image. Then load this image during JVM initialization.
> This means building some sort of AOT infrastructure. I would like to
> avoid this for initial bring up if at all possible. Instead, I am
> thinking of forcing Jitrino.JET to jit all MMTK classes during JVM
> bootstrap. My guess is that this will slow down bootup by 1-2
> seconds. In other words, no biggie because we can always go back and
> clean this up once some else installs AOT infrastructure.
>
> One gotcha is that there can be no real garbage collection before MMTK
> has been JITed. Its not likely to be a big problem since
> bootstrapping a JVM does not burn up gigabytes of java heap.
>
> Thoughts?
>
> --
> Weldon Washburn
> Intel Middleware Products Division
>
> ---------------------------------------------------------------------
> Terms of use : http://incubator.apache.org/harmony/mailing.html
> To unsubscribe, e-mail: harmony-dev-unsubscribe@incubator.apache.org
> For additional commands, e-mail: harmony-dev-help@incubator.apache.org
>
>
If your´re not using MMTK as an allocator, I don't think this would be an issue.
---------------------------------------------------------------------
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: harmony-dev-unsubscribe@incubator.apache.org
For additional commands, e-mail: harmony-dev-help@incubator.apache.org