...and not just the SQL, but also the stuff that happens /between/ SQL statements, which increasingly is the part of applications these days that need the most work. Cary Millsap Hotsos Enterprises, Ltd. http://www.hotsos.com * Nullius in verba * Upcoming events: - Performance Diagnosis 101: 9/14 San Francisco, 10/5 Charlotte, 10/26 Toronto - SQL Optimization 101: 9/20 Hartford, 10/18 New Orleans - Hotsos Symposium 2005: March 6-10 Dallas - Visit www.hotsos.com for schedule details... -----Original Message----- From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Jared Still Sent: Tuesday, September 21, 2004 11:18 AM To: sjhussain@xxxxxxxxxxxxxxx Cc: oracle-l@xxxxxxxxxxxxx; oracle-l-bounce@xxxxxxxxxxxxx Subject: Re: calculate % of response time components Hi Syed, What is your basis for tuning? These numbers really don't tell you anything useful for tuning. 52 seconds of waits for direct path read sounds pretty good for a busy database that has been up for a few days. :) Might not be too good for a single OLTP transaction though. Is there a performance problem? Which SQL will you start with? It is unlikely that you can tweak any database parameters to improve the read times from disk. ( there are no silver bullets ;) If you have not read "Optimizing Oracle Performance" , I would suggest you get a copy; it will teach you how to identify performance problems, as well as how to predict how much time will be saved by tuning said 'problem' SQL. HTH Jared On Tue, 21 Sep 2004 16:58:53 +0300, sjhussain@xxxxxxxxxxxxxxx <sjhussain@xxxxxxxxxxxxxxx> wrote: act of the note are as follows: > > Top 5 Wait Events > > ~~~~~~~~~~~~~~~~~ > Wait % Total > > Event > Waits Time (cs) Wt > Time > > ------------------------ > -------------------- > ------------ > ------------ ------- > > direct path read > 4,232 10,827 > 52.01 > > db file scattered read > 6,105 6,264 > 30.09 > > direct path write > 1,992 3,268 > 15.70 > -- //www.freelists.org/webpage/oracle-l -- //www.freelists.org/webpage/oracle-l