You need to tune sqls which are bad in response time.
I mean, tune the sql which are taking too much time as response time.
response time = wait time + service time.
You may also take the top 3 queries from the statspack of order by
get(logical), physical gets and if possible tune them.
Jaffar
James Yang wrote:
> I download top expensive SQL from T_Code ST04 as follows:
>
> I want to know which kind of SQL should be observed at the first
> priority? The most total DiskRead, or most Reads/Exec, or most Execute
> times, or other?
>
> Tanks for any input.
>
>
>
>
>
>
>
> Execute DskRead Reads/Exec Bufgets Bgets/exec ProCrow Rproc/Exe Bgets/row
>
> 2 223,685 111,842.50 212,141 106,070.50 460,029 230,014.50 0.5
> 11 1215460 110,496.40 1532611 139,328.30 2,218,008 201,637.10 0.7
> 1 107,113 107,113.00 109,318 109,318.00 173,571 173,571.00 0.6
> 1 103,473 103,473.00 105,139 105,139.00 8,085 8,085.00 13
> 3 224,391 74,797.00 302,283 100,761.00 110,393 36,797.70 2.7
> 7 508,511 72,644.40 1,269,972 181,424.60 32,934 4,704.90 38.6
> 2 122,956 61,478.00 744,997 372,498.50 30,064 15,032.00 24.8
> 1 52,177 52,177.00 711,617 711,617.00 746 746 953.9
> 1 52,075 52,075.00 52,087 52,087.00 2,143 2,143.00 24.3
> 1 49,097 49,097.00 50,926 50,926.00 266 266 191.5
> 3 142,033 47,344.30 158,947 52,982.30 943 314.3 168.6
>
> more line........
>
> 13,654 12,917 0.9 73,632 5.4 77,776 5.7 0.9
> 11,684 8,950 0.8 47,286 4 27,577 2.4 1.7
> 8,532 7,163 0.8 168,497 19.7 40,284 4.7 4.2
> 269,636 191,984 0.7 6,747,996 25 1,348,179 5 5
> 11,543 7,616 0.7 221,314 19.2 49,784 4.3 4.4
> 8,427 5,683 0.7 223,087 26.5 10,789 1.3 20.7
> 104,827 63,722 0.6 2,100,330 20 524,135 5 4
>
> more lines.....
Received on Sun Jun 11 2006 - 04:10:09 CDT
