Oracle Database Performance Tuning Guide 10g
ISBN : -
Order a printed copy of this book from Amazon --UNAVAILABLE--
Cover Design - Oracle Database Performance Tuning Guide 10g
For your free electronic copy of this book please verify the numbers below.
(We need to do this to make sure you're a person and not a malicious script)
Sample Chapter From Oracle Database Performance Tuning Guide 10g
Copyright © Oracle Corp
Performance Principles
Performance tuning requires a different, although related, method to the initialconfiguration of a system. Configuring a system involves allocating resources in an
ordered manner so that the initial system configuration is functional.
Tuning is driven by identifying the most significant bottleneck and making the
appropriate changes to reduce or eliminate the effect of that bottleneck. Usually,
tuning is performed reactively, either while the system is preproduction or after it is
live.
Baselines
The most effective way to tune is to have an established performance baseline thatcan be used for comparison if a performance issue arises. Most database
administrators (DBAs) know their system well and can easily identify peak usage
periods. For example, the peak periods could be between 10.00am and 12.00pm and
also between 1.30pm and 3.00pm. This could include a batch window of 12.00am
midnight to 6am.
It is important to identify these high-load times at the site and install a monitoring
tool that gathers performance data for those times. Optimally, data gathering
should be configured from when the application is in its initial trial phase during
the QA cycle. Otherwise, this should be configured when the system is first in
production.
Ideally, baseline data gathered should include the following:
- Application statistics (transaction volumes, response time)
- Database statistics
- Operating system statistics
- Disk I/O statistics
- Network statistics
snapshots that are preserved for future comparisons. See 'Automatic Workload
Repository' on page 5-10.