| performance tuning [message #670855] |
Mon, 30 July 2018 03:53  |
alanm
Messages: 284
Registered: March 2005
|
Senior Member |
|
|
discovering the power of oracle statspack.
Available Tags
% of Busy CPU used for Instance:
Block changes:
consistent gets
CPU used by this session
DB time(s):
Physical reads:
Physical writes:
session logical reads
graphical analysis of statspack
[Updated on: Mon, 30 July 2018 03:54] Report message to a moderator |
|
|
|
|
|
|
|
| Re: performance tuning [message #670859 is a reply to message #670857] |
Mon, 30 July 2018 04:37  |
Roachcoach
Messages: 1576
Registered: May 2010
Location: UK
|
Senior Member |
|
|
Quite honestly I never look at them unless
a) There's been a significant deviation from normal behaviour - I know what the estate looks like and what it should look like
b) A user is complaining about something - usually dont need to go as far as DB stats for this.
c) It's a diff/"what has changed since X" exercise for analysis - self explanatory
d) Incident post mortem to find out what happened - a mixed bag, usually the "big ones" stop writing to these views anyway, they're often the first casualty
Almost always start with a diff between good and bad then look at the highlights and drill down from there. The process never changes, but the report areas sometimes do.
Reading them "just because" is the road to madness/compulsive tuning disorder in my opinion.
Edit: I should add that in my old age, a diff tends to be my second port of call because with enough time you'll find that 99/100 times you already know where to look based on what you've seen in real time/been told/top wait events.
[Updated on: Mon, 30 July 2018 04:46] Report message to a moderator |
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
