This week's book giveaway is in the Design forum.
We're giving away four copies of Building Microservices and have Sam Newman on-line!
See this thread for details.
The moose likes Performance and the fly likes Different JVM Vendors and their performances Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

Win a copy of Building Microservices this week in the Design forum!
JavaRanch » Java Forums » Java » Performance
Bookmark "Different JVM Vendors and their performances" Watch "Different JVM Vendors and their performances" New topic

Different JVM Vendors and their performances

Ravi Kiran Va
Ranch Hand

Joined: Apr 18, 2009
Posts: 2234


I want to know what are the various JVM implementations exist in the market and their performance comparisons.

Which of the JVM implementation is most popular on windows platforms?

Also is their any JVM provider that is better than SUN JVM .

Save India From Corruption - Anna Hazare.
William Brogden
Author and all-around good cowpoke

Joined: Mar 22, 2000
Posts: 13007
The Sun implementation is easily the most common version on Windows.

It has been years since I saw a JVM speed shootout documented. I get the impression that alternate JVMs have been optimized for different environments - for example the Dalvik VM used in Android phones.

Peter Johnson

Joined: May 14, 2008
Posts: 5852

Other common JVMs for Windows include the IBM JVM and JRockit (was from BEA, now Oracle).

For JVM performance comparisons, see the specjbb web site:

JBoss In Action
Ravi Kiran Va
Ranch Hand

Joined: Apr 18, 2009
Posts: 2234

Thank you very much .
Tim Holloway
Saloon Keeper

Joined: Jun 25, 2001
Posts: 17046

"Better", as I've already remarked once this morning, is a relative term. So Bill and I concur. IBM's jikes JVM used to be considered hot stuff, but I don't actually know these days. I try not to code so "close to the wire" that it makes that much difference. Usually a better algorithm makes all the difference.

One thing I did notice on the Android coding guidelines were that a number of their low-level optimization recommendations shouldn't be applicable when compiling with a modern-day Java compiler. In other words, the compiler would normally have taken care of the issue before the JVM ever had to worry about it. Which worries me. Do they know something I don't, or do they just "know" something?

An IDE is no substitute for an Intelligent Developer.
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link:
subject: Different JVM Vendors and their performances
It's not a secret anymore!