Yes, our db perfomance stinks to high heaven.
Mainly I believe this to be poor sql writing and have been
re-writing sql and tracing application sessions to
find the bottlenecking code that the developers wrote.
Other than that I have been running statspack, but the
trace files show a lot more about what is happening.
Currently the CPU and DISK usage on the server goes crazy
when you run through the application.
I guess I am asking why the application trace
shows those statistics, but when I run a trace
on a seperate session I get the below stats.
What is the difference and why are theyso different?
PHP Code:select count(*)
from
dual
call count cpu elapsed disk query current rows
------- ------ -------- ---------- ---------- ---------- ---------- ----------
Parse 1 0.00 0.00 0 0 0 0
Execute 1 0.00 0.00 0 0 0 0
Fetch 2 0.01 0.00 0 3 0 1
------- ------ -------- ---------- ---------- ---------- ---------- ----------
total 4 0.01 0.00 0 3 0 1
Misses in library cache during parse: 0
Optimizer goal: CHOOSE
Parsing user id: 53
Rows Row Source Operation
------- ---------------------------------------------------
1 SORT AGGREGATE (cr=3 r=0 w=0 time=255 us)
1 TABLE ACCESS FULL DUAL (cr=3 r=0 w=0 time=241 us)
********************************************************************************




Reply With Quote