We have a four node vmware ESX cluster built from HP BL495C blade server. Each blade contains two AMD Opteron 2435 CPU's (six core, 2600Mhz)
Just watched Brent Ozar's web cast on "sleepy cpu's" and after the recent stackoverflow problems I thought I'd check out my server.
CPU-Z reports a core speed of 528Mhz!
Does this look like it could be the same problem or is ESX doing tricks on me?
Specs:
Windows 2008, 4 vCPU, 4GB RAM. Storage is a SAN RAID10. Screenshot shows the server running a couple of 7zip processes to get the CPU high.
Update:
Looks like our cluster has been configured based on recommendation of this document page 5. Also the ESX vsphere configuration is saying that "Power Management Technology" s "Not available". Does that mean it defaults to "snooze mode"?
Update:
Different software… different result.
Best Answer
Guy - There are two kinds of power management, one is c states (i.e. c1enhance for intel - something similar for amd), and the other is p states (cool 'n quiet for amd). Is this 'CPU power management' listed under advanced software features in your conifiguration -or are you seeing this somewhere else? If CPU power management is disabled that might mean you already have cool 'n quiet disabled in your bios.
Power.CpuPolicy should be set to static if you want cpuz to read the clock frequency. However - dynamic 'dynamically' scales frequency up and down. It may make sense cpuz reads only 528Mhz - your server will run at the lowest frequency necessary to accomplish the current task.
See Faq 1 at CPUZ . Maybe try running a load on your server and then see if the frequency scales up. If it is not scaling you will need to do 2 things to (possibly) fix them:
Do the same for C1Enhanced in the bios if the above doesn't work. If you do this you will be running hotter / more power (if you server is constantly idle). These settings don't really matter if your server CPU is utilized fully (near 75%+ constant CPU load- i.e. you can't save any power if you're always running close to 100%!).
Finally - CPUZ is not a great choice for determining processor specs in a vm. You should use some benchmarking software (SPEC) to get an accurate understanding of what your processor is doing! I have windows machines under ESXi that read all kinds of weird ( some read 50% max cpu utilization when it is 100%- some get confused if you add/remove processors/ switch to a computer with higher/lower base clock speeds), so I wouldn't rely on any software based CPU gauges. You really need to run a benchmark to give you an understanding of whats actually going on, as there is too much between you and the CPU when virtualizing!