Java/JVM (HotSpot): Is there a way to save JIT performance gains at compile time?

When I measure the throughput of my Java application, I see a 50% performance increase over time:

• For the first 100K messages, I get ~3,000 messages per second
• For the second 100K messages, I get ~4,500 messages per second.

I believe the performance improves as JIT optimizes the execution path.

The reason given for not saving the JIT compilation is that "the optimizations that the JVM performs are not static, but rather dynamic, based on the data patterns as well as 开发者_如何学JAVAcode patterns. It's likely that these data patterns will change during the application's lifetime, rendering the cached optimisations less than optimal."

However, I know for a fact that these data patterns won't change during my application's lifetime, or even over multiple application lifetimes. So how can I "save" these performance gains in the HotSpot JVM?

See also, the relevant question and discussion.

You could try adapting your app to run it with Nailgun. Instead of invoking your app against a fresh JVM each time you invoke it against a Nailgun server which is a long-lived JVM. The second time you invoke your app, the nailgun JVM will have optimized the paths in your classes and should therefore execute a lot faster than it would from fresh.

Use '-server' to do much more up front. Hotspot does not as far as I know allow for saving jit information between runs so -server is the simplest way to tell it what you want it to do.

Are you sure it is CPU related and not IO related? I have seen this behaviour a lot of times, when hitting a cold cache somewhere worsens performance.

Few more options to tune up the JIT.

1. Class Data sharing http://publib.boulder.ibm.com/infocenter/javasdk/v6r0/index.jsp?topic=%2Fcom.ibm.java.doc.user.aix64.60%2Fuser%2Fclassdatasharing.html

2. Tiered Compilation See details for flag -XX:+TieredCompilation

3. Custom CompileThreshold Controls number of invocations of a function that would make it eligible for JIT compile. See details for flag -XX:CompileThreshold. Never make this to ZERO or ONE. Your tampering here may result in deterioration of performance. JVM gives you the option though. -server defaults this to 10000.