Re: buffer hit cache ratio should be ...

"Ibrahim DOGAN" <idogan_tech_at_yahoo.com> wrote in message news:6bf58828.0312240545.7865dd29_at_posting.google.com...
> Frank van Bortel <fbortel_at_nescape.net> wrote in message news:<bsae44$8t5
> > In other words: don't bother. I'd worry if users start complaining,
> > and run then statspack - or HotSos's tools.
> >
> that's so bad if you find out the issues about your databases when
> users start complaining about them.. Look up the term "proactive DBA"
> in your DBA dictionary...
>
> DBAs should promote continous monitoring to fix the problems before
> they surface to user community instead of sitting back, waiting the
> time users start screaming around about the performance...

Fine. But what do we monitor? I'd suggest that the only things that really count are

1. Response time of key business processes.
2. Throughput for key business processes.

The problem with monitoring changes in ratios is that it doesn't really tell you anything useful about the end-user experience. It might alert you to the fact that *something* has happened, but it will likely not tell you what. Of course identifying what the key business processes are and how long they take and what their volume is is much more difficult than calculating stats for a dashboard.

-- 
Niall Litchfield
Oracle DBA
Audit Commission UK