On Mon, 17 Dec 2007 10:53:28 -0600, McKown, John wrote: >... I want to ensure that non-production work will receive CPU >cycles. What is really wanted to to say that production batch will >receive 60% of the cycles, Model office about 20% and test about 10%.
Yuck! What kind of goal is that? I would suggest that you look at response time goals. figure out what your test jobs look like. Figure out what percentage of them are relativeely quick compiles and short tests. Then decide what kind of turnaround time you'd like to give them. Use that to specify a response time goal. Great precision is not needed. Suppose that you'd like your quick compiles to finish in ten minutes. That's a pretty modest goal. Maybe you find that about a quarter of your test jobs are long running jobs. Don't worry about it. Just set your response time goal to be 75% completion in ten minutes. Once you get it set up, you might find that you need to make adjustments. Does everyone submit a long running test just before going to lunch? Maybe you need to lower the percentile. Is test interfering too much with production? Maybe your ten minute response time goal is too agressive. I hope this helps. -- Tom Marchant ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
