As a Jr. wanting to be Sr. (someday) I have to ask the stupid questions:
why is Buffer % bad? Dont you want 100% buffer cache hit vs. 100% disk i/o?
looks like you got some nasty sql in there (a buffer cache of 100% is not a good thing, looks like you are doing much logical io)
Anyway, does web logic cache its statements for you, usually a parameter withing the database connections properties
On 06/06/06, Sandeep Dubey <dubey.sandeep@xxxxxxxxx> wrote: > > > Rollback per transaction %: 44.17 > Buffer Nowait %: 100.00 Redo NoWait %: 99.97 > Buffer Hit %: 100.00 In-memory Sort %: 100.00 > Library Hit %: 100.00 Soft Parse %: 100.00 > Execute to Parse %: 9.62 Latch Hit %: 99.88 > Parse CPU to Parse Elapsd %: 69.06 % Non-Parse CPU: 91.60 > > With 100% soft parse, execute to parse ratio is so low. Is it bad, how > I can I improve it? > > I see rollback per transaction as 44.17. We are using Hibernate that > generates database mapping and produces most of the SQLs. How can I > invetigate further? But I doubt if application is doing some big time > rollbacks.
-- Bryan S Wells Cell: 303.532.9879 Email: bunjibry@xxxxxxxxx