Previous |
Next |
Performance improvement is an iterative process. Removing the first bottleneck (a point where resource contention is at its highest) might not lead to performance improvement immediately because another bottleneck might be revealed that has an even greater performance impact on the system. For this reason, the Oracle performance method is iterative. Accurately diagnosing the performance problem is the first step toward ensuring that the changes you make to the system will result in improved performance.
Performance problems generally result from a lack of throughput, unacceptable user or job response time, or both. The problem might be localized to specific application modules or span the system. Before looking at database or operating system statistics, it is crucial to get feedback from the system users and the people paying for the application. This feedback makes it easier to set the performance goal. Improved performance can be measured in terms of business goals rather than system statistics.
The Oracle performance method can be applied until performance goals are met or deemed impractical. Because this process is iterative, some investigations may have little impact on system performance. It takes time and experience to accurately pinpoint critical bottlenecks in a timely manner. Automatic Database Diagnostic Monitor (ADDM) implements the Oracle performance method and analyzes statistics to provide automatic diagnosis of major performance problems. Because ADDM can significantly shorten the time required to improve the performance of a system, it is the method used in this guide.