Our Oracle-focused solutions will concentrate on service time, queue time, or both. One solution to reduce the scattered read waits is to increase Oracle's buffer cache. There is plenty of memory, and (as shown shortly) there is also plenty of CPU available to handle the possible increase in cache management resources. Based on the size of the tables involved, a 1GB buffer cache should be able to cache the entire customer table.

Because the total queue time accounts for nearly 30% (28.9%) of the total response time, if queue time is eliminated, total response time could improve by as much as 30%. But there will likely be some other queue time, so to be conservative; let's say we anticipate a 20% decrease in queue time.

Total service time accounts for nearly 70% of the sample interval's total response time. Clearly, there is a opportunity here for improvement. How we reduce the service time may not be so easy in practice. While there are possibilities to reduce service time from both an operating system and an application perspective, from an Oracle perspective, a straightforward tweak is not apparent. This is not a problem because of the potentially massive performance improvement achieved by increasing the buffer cache to reduce the total queue time and also by tuning key CPU-intensive SQL statements (as explained in the discussion of the next analysis cycles).