The generic rules of thumb: 1. Don't define more virtual cpus than you have real available. 2. Don't define more virtual cpus than you need.
With Websphere: Two cpus or more are best. Websphere has a process, in which two tasks talk to each other. If each process has a cpu then they don't have to steal the processor from one another. I think this hint came out in the SLES8 or SLES9 days. That is the timeframe that I downloaded Websphere and had an official "interest" in it...i.e. there was a project coming up. <G> Given that was a while back, things may have changed. Tom Duerbusch THD Consulting >>> Mark Post <[email protected]> 4/25/2011 12:09 PM >>> >>> On 4/25/2011 at 09:34 AM, "Dean, David (I/S)" <[email protected]> wrote: > Can some of you weigh in on the merits (demerits) of defining multiple CPU's > to virtual Linux boxes? We are heavy WebSphere and have gotten differing > opinions. The typical advice is that if you are driving a single CPU over 80%, then a second one would likely be useful. Otherwise, you just add to z/VM's workload to schedule that virtual CPU with no benefit to the guest. Mark Post ---------------------------------------------------------------------- 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 more information on Linux on System z, visit http://wiki.linuxvm.org/ ---------------------------------------------------------------------- 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 more information on Linux on System z, visit http://wiki.linuxvm.org/
