|
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
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.