"warming up" Java HotSpot

I've been running some server-side benchmarks and noticed that I need to "warm up" the application by running it several time before I get consistent numbers. I believe that part of this has to do with the VM optimizing things. Any insight on the role HotStop has to play with this warming up period would be greatly appreciated.

[344 byte] By [tocatlian] at [2007-9-26 1:54:03]
# 1
HotSpot (not HotStop!) starts by interpreting bytecodes. After a while, it decides which methods to compile into native code. This means that methods will start running slowly, then there will be a slight pause while it's compiled, then it will run faster.
schapel at 2007-6-29 3:06:01 > top of Java-index,Java HotSpot Virtual Machine,Specifications...