| OT: NexT Gen JVM [message #573834] |
Tue, 27 August 2002 11:41 |
 Radu
Messages: 44
Registered: July 2009 |
Member |
|
|
Hello everybudy,
If IBM opens now new windows of performance for desktop computing in Java
with the help of SWT/Jface technologies I wonder if it has any plans on
updating its JVM to respond to speed requirements of modern JIT ed
platforms.
For quite a while I've been hearing about how cool JVM will be in the near
future, about technologies that will made JVM better than native code.
One of them is unfortunatly implemented in .NET as a result of M$
"inventivity".
As i know the Java is based in this era on a HotSpot implemetation wich uses
some kind of smart profiling and JIT - interpreted code runing states. This
is cool tech but suks every time on startup of any application.
This is due to the fact that every time you run a java app the JVM makes the
same steps.
..NET uses a JIT only tech and fools the user by imediatly translating the il
code to native and saving the optimizad code for later running. this is so
called assembly.
This feature is neat and could save a bounch of seconds for application
start-up times. Why then not implemet an method of saving profiled and
native data for every app that jvm runned in a special folder for later
refference and usage.
Another trick that could make JVM not suck is to minimize the amount of
memory that it consumes.
Today we know that for each java app we must lauch a separate JVM as a
separate app wich does the same thing TM for every app. This sucks big time!
Why not make a system based on JVM code sharing for every java app. We could
have a process (os proccess) or deamon that is the jvm wich instantiates the
HotSpot and GC components for java apps that it runs. the java.exe will be a
boot strap app that tels that process to create a new instance of hotspot
and GC for that app, not to load an completly new jvm.
Glad to hear your comments,
Regards.
Radu
|
|
|
Powered by
FUDForum. Page generated in 0.03970 seconds
] 
Search
Help
Register
Login
Home
