RE: High Resource consuming SQL in Statspack ?
- From: VIVEK_SHARMA <VIVEK_SHARMA@xxxxxxxxxxx>
- To: "kmoore@xxxxxxxxxxxx" <kmoore@xxxxxxxxxxxx>
- Date: Thu, 27 Nov 2008 21:49:34 +0530
Thanks Keith for your support
Elapsed (Time between the Snapshots): 20.12 (mins)
Qs Is there a threshold value above which %Total may be considered BAD? ... My
impression is %Total > 30% is BAD.
Cheers
-----Original Message-------------------------
From: Keith Moore [mailto:kmoore@xxxxxxxxxxxx]
Sent: Thursday, November 27, 2008 9:42 PM
Vivek,
What time period is the snapshot for?
I've seen application running on application servers that make this call
frequently.
Each execution is only about 5 milliseconds but there are over 13,000
executions. It the snapshot time period is something like 2 hours then I would
conclude that the % of total is high because not much else is happening and
it's nothing to worry about.
Keith
> P.S. Bad SQL:-
>
> SQL ordered by CPU DB/Inst: LOSDB/LOSDB Snaps: 552-554
> -> Resources reported for PL/SQL code includes the resources used by all SQL
> statements called by the code.
> -> Total DB CPU (s): 121
> -> Captured SQL accounts for 78.9% of Total DB CPU
> -> SQL reported below exceeded 1.0% of Total DB CPU
>
> CPU CPU per Elapsd Old
> Time (s) Executions Exec (s) %Total Time (s) Buffer Gets Hash
> Value
> ---------- ------------ ---------- ------ ---------- ---------------
> ----------
> 60.09 13,016 0.00 49.7 60.10 0
> 1702556642
> Module: JDBC Thin Client
> SELECT VALUE FROM NLS_INSTANCE_PARAMETERS WHERE PARAMETER ='NLS_DATE_FORMAT'
**************** CAUTION - Disclaimer *****************
This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely
for the use of the addressee(s). If you are not the intended recipient, please
notify the sender by e-mail and delete the original message. Further, you are
not
to copy, disclose, or distribute this e-mail or its contents to any other
person and
any such actions are unlawful. This e-mail may contain viruses. Infosys has
taken
every reasonable precaution to minimize this risk, but is not liable for any
damage
you may sustain as a result of any virus in this e-mail. You should carry out
your
own virus checks before opening the e-mail or attachment. Infosys reserves the
right to monitor and review the content of all messages sent to or from this
e-mail
address. Messages sent to or from this e-mail address may be stored on the
Infosys e-mail system.
***INFOSYS******** End of Disclaimer ********INFOSYS***
Other related posts:
