Re: High shared pool usage

Laimutis,
660 hard parses a minute in an OLTP is not bad? I thought it was a bad
number. Out of curiousity, what kind of hard parsing do other listers have
seen in best/worst/normal cases. (I realize that this could be dependent on
the application, design, the workload, etc). Has anyone imposed size
restrictions on shared pool like Brent has suggested.

I like David's (Kurtz) idea of setting a minimum value for buffer cache so
it does not get stolen.

Thanks.

On Tue, Sep 27, 2011 at 2:04 AM, <Laimutis.Nedzinskas@xxxxxx> wrote:

> > more than a million hard parse
> a day. That number looks too much to me. This is an OLTP financial
> application. Any comments?
>
> Comment 1: that's about 11.5 hard parses a second. Not that bad.
>
> Comment 2: looking into counters is good but looking into time spent is
> even better: first comes hard parsing time then contention: lathing on pool
> structures, etc. Specially at hard parsing peak times.
>


--
http://www.freelists.org/webpage/oracle-l

Other related posts: