On Monday, 10/15/2007 at 10:34 EDT, Richard Corak <[EMAIL PROTECTED]> wrote:
> >I suppose we should knuckle down and define a new eHG (e-holy grail) that > >is a function of CPU speed, disk access time, bus latency, memory latency, > >number of peripherals, wind direction, amount of local disk storage, > >number of tape drives, power consumption (kwh), mean age of programmers > >who wrote the code you're running, and the number of cubic meters it all > >occupies based on cabinet dimensions, the air-speed of an unladen > >*African* swallow (in April, of course), and total length of cables. > > Is this called a benchmark? No no no. I specifically emphasized the use of the African swallow in *APRIL*. eHG is a calculation of the number of virtual machines you can run with *your* workload at acceptable performance and total machine utilization of 94%, plus or minus 2%. Sorry for the 2% variability, but that's what you get when you introduce wind direction. (I can understand your mistake since so many people use the European swallow or fail to use April in their calculations. Tricksy, it is.) Alan Altmark z/VM Development IBM Endicott
