I dunno. I could easily design a cpu intensive workload (branch on count, anyone?) that could achieve and maintain a very high velocity for very long periods of time. I could pretty much guarantee that it could get over 80% using samples during just about any period, provided it was given a high enough importance.
I'd expect calculation-heavy engineering jobs to perform in a similar manner. I would agree, however, that any I/O heavy workload would struggle to ever cap 50% velocity and stay there. Gary p.s. I hesitate to say never anymore, though I do still use the word occasionally. -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] Behalf Of Ted MacNEIL Sent: Tuesday, September 27, 2005 7:00 PM To: [email protected] Subject: Re: A quick question about velocity goals set high >Empirically, if you don't have I/O as part of the velocity equation, you can never achieve a velocity of more that 45-50. ---------------------------------------------------------------------- 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
