Rob, On ESAXACT, that would be CPU? Waiting for CPU? Betsie -----Original Message----- From: Linux on 390 Port [mailto:[email protected]] On Behalf Of Rob van der Heij Sent: Wednesday, December 31, 2008 9:42 AM To: [email protected] Subject: Re: VMSTAT steals
On Wed, Dec 31, 2008 at 5:06 PM, Spann, Elizebeth (Betsie) <[email protected]> wrote: > We see high steal time when our virtual machines have multiple virtual > CPU's (but equal to or less than the number of real engines on the > LPAR) and the number of virtual CPU's defined in total are more than > the number of real engines. We are also over committed for memory. > In the ESALPS ESALNXV report, some of the virtual machines > consistently use less than the number of virtual CPU's defined. > Could this also be a case of wait-on-myself? Hard to tell from here. Not every application can use multiple CPUs. ESAXACT should show you what you're waiting for, but that's not always obvious for virtual machines that implement their own multi-programming. You're most welcome to upload an hour of data for use to analyze. That's part of the deal... (hey, we even do so once for folks who are not yet our customer) Rob -- Rob van der Heij Velocity Software http://www.velocitysoftware.com/ ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
