The charts in this section illustrate a number of "Trader" benchmarks that were run under different time periods and with various GC and thread configurations.
The following histograms show the total number of Trader operations for various latencies using JRockit DetGC, first with eight threads and then with sixty-four threads.
The following charts correspond to the previous JRockit DetGC histograms. The first chart summarizes Trader performance for JRockit DetGC with eight threads, while the second does the same but with sixty-four threads. The top black line in each chart shows throughput according to the right-hand scale (the higher the better). The bottom red and blue lines in each chart show application response times according to the left-hand scale (the lower the better).
The following style charts demonstrate the difference between the WLRT JRockit JVM and the Sun JVM over a two-hour period. Once again, the top black line in each chart shows throughput according to the right-hand scale, while the bottom red and blue lines in each chart show application response times according to the left-hand scale.
The following three histograms show the total number of Trader operations for various latencies using JRockit DetGC, Sun IncGC, and JRockit without DetGC, all with eight threads.
The following two charts show JRockit GC pauses as reported by its verbose GC output.
The results of this benchmark show that the WLRT 1.0 JRockit JVM with DetGC performed better than the Sun JVM with IncGC and the default JRockit JVM without DetGC in both throughput and latency. In fact, WLRT with JRockit DetGC was able to greatly reduce latency while maintaining a high level of throughput.
In addition, without DetGC, JRockit reported GC pauses as great as 275 milliseconds, but with DetGC, JRockit reported far lower maximum GC pause times of approximately 30 milliseconds.
Tom Barnes is a senior software engineer on BEA's WebLogic Performance Team and is the author of the "BEA WebLogic JMS Performance Guide" white paper on Dev2Dev.