Power Management in Windows Server 2008 SP2

Enabling the C-states in ESX 5i might bring the Opteron 6276 an improved performance/watt ratio. The question is whether the low power consumption at light loads will negate the performance impact. Although power consumption is lowered by using the "C-state enable" tweak, it is not spectacular: 10% lower energy consumption in idle will probably not give the Opteron 6276 an amazing performance/watt ration in ESXi. The impact of this tweak will make a difference in our EWL testing, not in the "full speed ahead" benchmarks. Also, our vApus FOS EWL testing showed that the Xeon consumed 25% less energy, so it will remain ahead.

As the virtualization benchmarks require more time to run, we will have to delay investigating them for a later article. But what about Windows 2008 R2? The idle power of the Opteron 6276 was excellent there. So which power policy should be chosen in Windows 2008? We compared Opteron performance in "High performance" to the Opteron 6276 performance when the power management policy was set to "Balanced.

  Opteron 6276
"High Performance"
Opteron 6276
"High Performance"
+ C6 enable.
Xeon X5670
"High performance" vs.
Xeon X5670 "Balanced"
Cinebench Single-threaded +16% +18% +1%
Cinebench Multi-threaded +5% +5% +1%
Blender +4% +13% +1%
Encryption/Decryption AES +43% / +42% +43% / +44% +28% / +28%
Encryption/Decryption Twofish/Serpent +8% / +8% +8 / +8% +0 / +0%
Compression/decompression +9% / +4% +9 / +4% +0 / +2%

If we combine the our idle power consumption measurements with these numbers, things get a lot clearer. The "balanced" power policy disables turbo. Therefore, the maximum performance boost from enabling "high performance" should be 13%. The TrueCrypt benchmarks show much larger increases (see (*)), which we honestly don't understand. The performance boost (40%) is only possible if the CPU boosts to 3.2GHz, but that is not supposed to happen. First, the TrueCrypt software is well threaded and uses all clusters (32 threads). Second, we disabled C6, so normally the CPU is not able to boost to 3.2GHz. Third, our monitoring clearly indicated a 2.6GHz clock as expected.

We also did a quick x264 4.0 benchmark (1st pass) which is lightly threaded and showed the same performance (46%!) increase by simply switching from "Balanced" to "High performance" (turbo limited to 2.6GHz, no C6). The Xeon only got a 13% increase in performance..

Closer monitoring reveals that "Balanced" frequently reduces the cores to 1.4GHz. So we have a similar situation as the one where we found power management problems on the AMD "Istanbul" Opteron when the power policy was set to "Balanced".

Basically "Balanced" brings the clock speed down to a low P-state even when a thread is demanding the maximum processing power. Or in other words, the power manager is too eager to bring the clock speed down instead of looking ahead: the polling is blind for the very near future. The result is that quite often the workload gets processed at 1.4GHz (for a short time).

In contrast, the high performance setting does not make use of frequency scaling besides Turbo. So the CPU runs at 2.3GHz at the very minimum and frequently reaches 2.6GHz. So if you buy an Opteron 6200 server, it is strongly advised to chose the "High Performance" setting. Under light load, the balanced power manager saves a few percentage of power running idle, but in our opinion, it is not worth the large performance degradation. Notice also that the Xeon hardly suffers from the same problem with the exception of the AES-NI enabled TrueCrypt bench, and even then the performance impact is significantly lower.

In a nutshell: the power policy "Balanced" strongly favors the Xeon as the performance impact is non-existent or much lower. Let us see some raw performance numbers.

Measuring Real-World Power Consumption, Part Two Rendering Performance: Cinebench
Comments Locked

106 Comments

View All Comments

  • duploxxx - Thursday, November 17, 2011 - link

    Very interesting review as usual Johan, thx. It is good to see that there are still people who want to thoroughly make reviews.

    While the message is clear on the MS OS of both power and performance i think it isn't on the VMware. First of all it is quite confusing to what settings exactly have been used in BIOS and to me it doesn't reflect the real final conclusion. If it ain't right then don't post it to my opinion and keep it for further review....

    I have a beta version of interlagos now for about a month and the performance testing depending on bios settings have been very challenging.

    When i see your results i have following thoughts.

    performance: I don't think that the current vAPU2 was able to stress the 2x16core enough, what was the avarage cpu usage in ESXTOP during these runs? On top of that looking at the result score and both response times it is clear that the current BIOS settings aren't optimal in the balanced mode. As you already mentioned the system is behaving strange.
    VMware themselves have posted a document for v5 regarding the power best practices which clearly mentions that these needs to be adapted. http://www.vmware.com/files/pdf/hpm-perf-vsphere5....

    To be more precise, balanced has never been the right setting on VMware, the preferred mode has always been high performance and this is how we run for example a +400 vmware server farm. We rather use DPM to reduce power then to reduce clock speed since this will affected total performance and response times much more, mainly on the virtualization platform and OEM bios creations (lets say lack of in depth finetuning and options).

    Would like to see new performance results and power when running in high performance mode and according the new vSphere settings....
  • JohanAnandtech - Thursday, November 17, 2011 - link

    "l it is quite confusing to what settings exactly have been used in BIOS and to me it doesn't reflect the real final conclusion"

    http://www.anandtech.com/show/5058/amds-opteron-in...
    You can see them here with your own eyes.
    + We configured the C-state mode to C6 as this is required to get the highest Turbo Core frequencies

    "performance: I don't think that the current vAPU2 was able to stress the 2x16core enough, what was the avarage cpu usage in ESXTOP during these runs?"

    93-99%.

    "On top of that looking at the result score and both response times it is clear that the current BIOS settings aren't optimal in the balanced mode."

    Balanced and high performance gave more or less the same performance. It seems that the ESX power manager is much better at managing p-states than the Windows one.

    We are currently testing Balanced + c-states. Stay tuned.
  • duploxxx - Thursday, November 17, 2011 - link

    thx for answers, i read the whole thread, just wasn't sure that you took the same settings for both windows and virtual.

    according to Vmware you shouldn't take balanced but rather OS controlled, i know my BIOS has that option, not sure for the supermicro one.

    quite a strange result with the ESXTOP above 90% with same performance results, there just seems to be a further core scaling issue on the vAPU2 with the performance results or its just not using turbo..... we know that the module doesn't have the same performance but the 10-15% turbo is more then enough to level that difference which would still leave you with 8 more cores

    When you put the power mode on high performance it should turbo all cores for the full length at 2.6ghz for the 6276, while you mention it results in same performance are you sure that the turbo was kicking in? ESXTOP CPU higher then 100%? it should provide more performance....
  • Calin - Friday, November 18, 2011 - link

    You're encrypting AES-256, and Anand seem to encryrpt AES-128 in the article you liked to in the Other Tests: TrueCrypt and 7-zip page
  • taltamir - Friday, November 18, 2011 - link

    Conclusion: "Intel gives much better performance/watt and performance in general; BD gives better performance/dollar"

    Problem: Watts cost dollars, lots of them in the server space because you need to some some pretty extreme cooling. Also absolute performance per physical space matters a lot because that ALSO costs tons of money.
  • UberApfel - Sunday, November 20, 2011 - link

    A watt-year is about $2.

    The difference in cost between a X5670 & 6276; $654

    On Page 7...
    X5670: 74.5 perf / 338 W
    6276: 71.2 perf / 363 W

    adjusted watt-per-performance for 6276: 363 * (74.5 / 71.2) = 380

    difference in power consumption: 42W

    If a server manages an average of 50% load over all time; the Xeon's supposed superior power-efficiency would pay for itself after only 31 years.

    Of course you're not taking into consideration that this test is pretty much irrelevant to the server market. Additionally, as the author failed to clarify when asked, Anandtech likely didn't use newer compilers which show up to a 100% performance increase in some applications ~ looky; http://www.phoronix.com/scan.php?page=article&...
  • Thermalzeal - Monday, November 21, 2011 - link

    Good job AMD, you had one thing to do, test your product and make sure it beat competitors at the same price, or gave comparable performance for a lower price.

    Seriously, wtf are you people doing?
  • UberApfel - Tuesday, November 22, 2011 - link

    Idiots like this is exactly why I say the review is biased. How can anyone with the ability to type be able to scan over this review and come to such a conclusion. At least with the confidence to comment.
  • zappb - Tuesday, November 29, 2011 - link

    completely agree - some very strange comments along these lines over the last 11 pages
  • zappb - Tuesday, November 29, 2011 - link

    posted by ars technica - incredibly tainted in intels favour

    The title is enough:

    "AMD's Bulldozer server benchmarks are here, and they're a catastrophe"

Log in

Don't have an account? Sign up now