A reader, July 19, 2016 - 11:31 am UTC
Here
buffer_gets and executions and elapsed_time value is byte , byte and micro second respectivily.
July 19, 2016 - 2:06 pm UTC
Executions isn't measured in bytes! It's just a count of how many times you executed it!
Chris
Hardik, July 20, 2016 - 6:47 am UTC
In organisation , plsql procedure written by other plsql developer. And DBA does not know what is inside the code and the what is a logic of the procedure.
My question is above case how Dba determine the plsql procedure is running slow?
July 20, 2016 - 9:32 am UTC
My question is above case how Dba determine the plsql procedure is running slow?
Slow is a relative term. If users are waiting for the results of the procedure, 1 minute is effectively forever. But if it's part of an overnight batch job, who cares?
It's your users that determine what "slow" is. Once you have this defined they can monitor runtime. PL/SQL calls appear in v$sqlstat too!
Hardik, July 20, 2016 - 12:02 pm UTC
Thank most useful me.
But when I set auto trace on.
1853418 consistent gets ( bytes )
89 recursive calls.
29779 bytes sent via sql net to client
1246 bytes received via sql net from client.
July 20, 2016 - 1:02 pm UTC
So... what are you hoping to learn from us?
Hardik, July 20, 2016 - 12:02 pm UTC
1001 rows processed