Re: does parse time cpu account for library cache waits?

NetComrade wrote:
>
> trying to convince developers to use binds more :)
>
> it turns out the database is spending 10%+ of CPU just parsing:
>
> CPU used by this session 59,509,459
> parse time cpu 7,048,429
>
> here are related library cache waits:
>
> select event, total_waits, total_timeouts, average_wait from
> v$system_event
>
> library cache pin 182269 1126 3.29589782
> library cache lock 27791 26112 294.223418
> library cache load lock 12471 4599 124.732179
> .......
> We use Oracle 8.1.7.4 on Solaris 2.7 boxes
> remove NSPAM to email

When you're trying to get a latch you can spin, which burns cpu or you can sleep which doesn't explicitly burn cpu (but of course may incur system cpu to swap in/out et al). Spinning doesn't contribute to the wait time stats in the various v$ views

hth
connor

-- 
=========================
Connor McDonald
http://www.oracledba.co.uk

"Some days you're the pigeon, some days you're the statue"