RE: disk arms (was RE: Tips for user ASP)

[Vernon Hamberg <vhamberg@xxxxxxxxx>]

DSPFD has activity counts, both physical and logical. Multiple logical to 1
physical means blocking. You can also get IO sizes from WRKDSKSTS, or from
some PEX trace data, I think.

At 08:31 AM 7/2/02 +1200, you wrote:
>Hi Scott
>
>as a matter of interest are these jobs designed to take advantage of
>blocking/sequential access to minimize disk access ?
>
>Anyone - is there a way to see that blocking is being utilized other than
>trying to use the open files WRKJOB display ?
>
>Regards
>Evan Harris
>
>>Charly,
>>
>>I use WRKDSKSTS and look at the % busy over a period of time, the guideline
>>is that this number be below 40%.  When we run certain jobs that move a lot
>>of data around this number will be over 40% on almost all drives when
>>sampled for a period of time.  I'm not sure how to dig out the other
>>information you have but I do know we have 12 of the 17GB drives in a single
>>ASP that is 50% full.  It took us awhile to figure out why the performance
>>would go bad at times but finally figured out what was happening.  I will
>>say that in general our performance is really good but we have certain jobs
>>that move a lot of data and they cause problems, we have even started trying
>>to run certain jobs at night to minimize the impact.
>>
>>Scott Mildenberger