On Tue, 1 May 2012 13:29:06 -0500, Mark Zelden <[email protected]> wrote:
>On Tue, 1 May 2012 10:28:33 -0500, Tom Marchant <[email protected]> >wrote: > >>IMO, most batch should be run in discretionary. The exception is >>workload with turnaround requirements. These should be met with >>response time goals. A "penalty" service class that is "just barely >>above discretionary" makes no sense at all to me. >> >>When WLM has plenty of discretionary work to do, it is able to get >>the most work out of the system. >> > >1) As someone already mentioned, there are legitimate applications >where batch is every bit as important as online / interactive work. >If you system is running at or near 100%, your not going to get >that batch work done at all, or not within SLAs if it is discretionary. Agreed. That's why I wrote "Most batch" and "The exception is workload with turnaround requirements" >2) While your idea may work fine in a 100% production LPAR only, >most shops have LPARs where there is a mixture. If all batch >is discretionary, what prioritizes production over test / development >batch? I didn't say "All" batch is discretionary. Also, not all production batch has the same requirements. >I agree that test batch should usually be set to discretionary. I say >usually because I'm sure there are some posts in the archives where >people have removed discretionary and given it a low importance >like 5 - and low velocity. You can search the archives for their >reasons. I don't like velocity goals except for long running address spaces. If I was going to do that, I would set a low response time goal. For example, in our environment, the vast majority of development jobs end in considerably less than a minute after being submitted. In this environment, if I wanted to set a low goal like you suggest, it might be 50% complete in less than 15 minutes. Remember that discretionary work is managed like a Mean Time To Wait group. IMO low priority work is managed better in discretionary than with either a low velocity goal or a low response time goal. -- Tom Marchant ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
