Linked by Thom Holwerda on Thu 14th May 2009 15:39 UTC
Thread beginning with comment 363768
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 06/13/13 14:35 UTC
Linked by Thom Holwerda on 06/11/13 17:07 UTC
Linked by Thom Holwerda on 06/10/13 23:13 UTC
Linked by Thom Holwerda on 06/08/13 14:57 UTC
Linked by Thom Holwerda on 06/07/13 11:40 UTC
Linked by Thom Holwerda on 06/04/13 12:45 UTC
Linked by nfeske on 05/31/13 10:12 UTC
Linked by Thom Holwerda on 05/29/13 16:59 UTC
Linked by Thom Holwerda on 05/24/13 17:26 UTC
Linked by Thom Holwerda on 05/21/13 21:38 UTC
More Features »
Sponsored Links



Member since:
2005-07-07
The major problem with Java/.Net (or most VMs for that matter) is not its speed, but rather the high memory requirements for initial JIT compiling of bytcodes whenever they are loaded and the GC tuning that is required to develop performance apps with it. A way around the JIT memory requirement is to do AOT. This would however not solve the GC problem and make your Java app non WORA.
The J2ME JVMs tend to interpret code when there isn't enough RAM to JIT compile classes. Some J2ME VMs, like the IBM J9, can accept AOT compiled classes that do not have the JIT overheads, but would only run on CPUs they were targeted for.
-Ad