|
|
Low overall throughput manifests for example as a low score in benchmarks, too few transactions executing per minute in a transaction based system or long processing times for large batches of data.
This chapter includes these topics:
A low overall throughput usually means that your JVM is not tuned to maximize application throughput. Before engaging in time-consuming troubleshooting and mitigation tasks, you should retune the Oracle JRockit JVM to optimize application throughput and restart the application. For detailed instructions on how to tune the JVM for optimal throughput, please refer to Tuning For Better Application Throughput
There is a certain trade-off between overall application throughput and low individual latencies. A JVM that is tuned for optimal overall throughput spends as little CPU time in garbage collection and memory management as possible to allow the Java application to run as much as possible. To minimize unnecessary overhead and extra work during garbage collection, the Java application should be paused for the duration of the entire garbage collection. This might cause long individual pauses; however, in the long run, it will maximize the overall throughput. You can reduce the latencies without losing too much overall throughput by, for example, limiting the compaction or using a generational garbage collector. See Tuning For Low Latencies for tips on how to reduce the garbage collection pauses.
If none of the tuning solutions suggested in Tuning For Better Application Throughput, resolve the problem, you will need to open a case with Oracle Support. You can find instructions on how to report a problem to Oracle, including the sort of information to include, in Submitting Problems to Oracle Support.
|