I don't think you need such performance hackers in Java. First, I would like to concentrate on writing readable code and using decent algorithms - this will bring more performance benefits than what you are discussing.
In most standalone applications, the vast majority of the time is spent sitting, waiting for the user to do something. In most web applications, the bytecode runtime in the JVM must be loaded by network time, database time, or business logic.
If you really care about the performance of part of your Java application, you can move it to JNI code and generally bypass the Java interpreter.
paxdiablo
source share