That is a very high, IMO, goal for batch. I would expect very little besides the system to have a higher priority. Does you Critical path use this HOTBATCH? How multi-threaded is your critical path? If 4 jobs don't run parallel, then the 4th CP is doing other work and you may find the answer is just the additional overhead switching another CP.
Dave Gibney Information Technology Services Washington State University > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Tom Marchant > Sent: Tuesday, March 20, 2012 12:17 PM > To: [email protected] > Subject: Re: Execution Velocity > > On Tue, 20 Mar 2012 11:05:25 -0500, gsg wrote: > > >Can someone please explain execution velocity for Workload Manager, I'd > really appreciate it. > > John Arwe's paper, for which Alan posted a link is excellent. > > >We do not seem to be getting the results we thought we > >would. On this particular LPAR, we we're running with 3CPs, > >but when we activated a 4th CP, our critical path ran longer. > >Overall we are pushing through more work, but our critical > >path window ran longer. We are stumped on why. We're > >starting to look at RMF data, but thought I would throw it > >out to see if anyone has any clues. > > Clues come from RMF data about how your goals are being met. > > >We have a HOTBATCH service class defined with IMP=1, > >Execution Velocity of 90, with the CPU Critical flag turned > >on. This service class has a jobclass assigned to it. At > >any given time during our batch window, there may be up > >to two of three of these jobs running. Other service class > >we have define for batch are PRDBATHI(IMP=2, Execution > >Velocity of 30) and PRDBATLO(Discretionary). > > It sounds as if you have turnaround time requirements for > these jobs. IMO, velocity goals are not the best for this kind > of workload. Have you considered response time goals? > > -- > Tom Marchant > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
