Steps in The Oracle Performance Improvement Method -- 性能调优的步骤
1. Perform the following initial standard checks: -- 初始标准的检查
a. Get candid feedback from users. Determine the performance project's scope
and subsequent performance goals, and performance goals for the future. This
process is key in future capacity planning.
-- 从用户那获得反馈
b. Get a full set of operating system, database, and application statistics from the
system when the performance is both good and bad. If these are not available,
then get whatever is available. Missing statistics are analogous to missing
evidence at a crime scene: They make detectives work harder and it is more
time-consuming.
-- 获取性能数据
c. Sanity-check the operating systems of all computers involved with user
performance. By sanity-checking the operating system, you look for hardware
or operating system resources that are fully utilized. List any over-used
resources as symptoms for analysis later. In addition, check that all hardware
shows no errors or diagnostics.
-- 详细的排查
2. Check for the top ten most common mistakes with Oracle Database, and
determine if any of these are likely to be the problem. List these as symptoms for
later analysis. These are included because they represent the most likely problems.
ADDM automatically detects and reports nine of these top ten issues.
-- 检查排名前10位的错误
3. Build a conceptual model of what is happening on the system using the symptoms
as clues to understand what caused the performance problems.
-- 列一张列表来发现具体的性能问题
4. Propose a series of remedy actions and the anticipated behavior to the system,
then apply them in the order that can benefit the application the most. ADDM
produces recommendations each with an expected benefit. A golden rule in
performance work is that you only change one thing at a time and then measure
the differences. Unfortunately, system downtime requirements might prohibit
such a rigorous investigation method. If multiple changes are applied at the same
time, then try to ensure that they are isolated so that the effects of each change can
be independently validated.
-- 将你锁需要处理的步骤列一张先后顺序表
5. Validate that the changes made have had the desired effect, and see if the user's
perception of performance has improved. Otherwise, look for more bottlenecks,
and continue refining the conceptual model until your understanding of the
application becomes more accurate.
-- 确保你所做的改变有生效
6. Repeat the last three steps until performance goals are met or become impossible
due to other constraints.
-- 重复3,4,5 使得性能要求得到满足