Java performance Issues (V) - Inconsistent JVM implementations

31 January 2008

When Java Programming Language was designed, the main goal was that the programs written using Java language should be able to run across different platforms securely. To be able to run programs written in Java language across different platforms securely, mainly depends upon Java Virtual Machine (JVM) implemented on those platforms. It means stability and version of Java Virtual Machine (JVM) is very important. However, only on platforms Solaris (Sun’s own platform), Linux, and Windows you will find most updated Java Virtual Machine (JVM). Where as HP and IBM provide their own implementation for their operating systems and found that it is not actively updated with the latest release of Java. The JVMs found on these platforms were even a year old.

Various JVM implementations

On Windows, there’s JVMs from Sun, IBM and Microsoft. The IBM one often has slightly higher performance, but when Sun releases a new specification, it takes a bit longer for IBM to implement it. The Microsoft JVM is totally obsolete (version 1.1.4). On Linux, there’s Sun, IBM, Blackdown and kaffe. The last two are open source efforts, though the Blackdown team works together closely with Sun. kaffe is not a complete implementation, most notably it lacks AWT/Swing support. On OS/2 there are JVM’s from IBM, GoldenCode Development, and Innotek Systems. On MacOS (and OS X) Apple does the JVM implementations IIRC. HP does the JVM implementation for HP-UX, and SGI for Irix. IBM’s implementation is the primary (and typically only) one for AIX, OS/400, and other IBM platforms.

Related Posts: