You can draw lpar busy vs velocity of the service class to see what it achieves when the lpar gets busy and get the number.
On Wed, 14 Oct 2020, 3:06 am Jerry Whitteridge, < [email protected]> wrote: > Dave - I'm by no means a Capacity Planning guru but here's my 2 cents. > > Velocity is defined as a measure of protection against delay - it's not a > hard and fast number. I'd first look at your service classes and find if > any of them have a PI of less than 1. If they do they are over achieving > their goals and you could drop the velocity on them to provide resources to > the service classes who are struggling. Adjust the Velocities by 10 rather > than single digits. All the tuning of the high achieving (not High > Importance or velocity) Classes will provide help to the under achievers. > > Jerry Whitteridge > [email protected] > Manager Mainframe Systems & HP Non-Stop > Albertsons Companies > > -----Original Message----- > From: IBM Mainframe Discussion List <[email protected]> On Behalf > Of Gibney, Dave > Sent: Tuesday, October 13, 2020 2:28 PM > To: [email protected] > Subject: EXTERNAL EMAIL: Max possible velocity? > > It has been quite some time since I had to worry about my WLM policy. > We've had ample capacity since 2007. Now, as We begin to wind down, we have > reduced our contracted MSU capacity. > We dropped from 15 to 12 on an 5 way z13S-N05. My WLM policy, last > seriously adjusted in 2007 when we moved to a z9-L03 has velocities ranging > from a high of 90 (Adabas, Imp 1) down to 5 (BATCH Imp 5) > We are experiencing just a minor amount of performance pain. It strikes me > that perhaps some of my higher velocity goals (90, 70, 60, 50) may be > unattainable under the now reduced capacity. > > What is the high end for possible, single threaded (Adabas) velocity here? > Or, where should I be reading in current manuals. I was better at this 15 > years ago. > > Dave Gibney > Information Technology Services > Washington State University > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > ________________________________ > Warning: All e-mail sent to this address will be received by the > corporate e-mail system, and is subject to archival and review by someone > other than the recipient. This e-mail may contain proprietary information > and is intended only for the use of the intended recipient(s). If the > reader of this message is not the intended recipient(s), you are notified > that you have received this message in error and that any review, > dissemination, distribution or copying of this message is strictly > prohibited. If you have received this message in error, please notify the > sender immediately. > ________________________________ > > ---------------------------------------------------------------------- > 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
