Overclocking Intel's New 45nm QX9650: The Rules Have Changed
by Kris Boughton on December 19, 2007 2:00 AM EST- Posted in
- CPUs
Will the Real QX9650 Power Consumption Please Stand Up?
The recent attention highlighting the conflicting manners in which Intel and AMD quote processor power consumption figures has generated a fair amount of discussion regarding which methodology more closely represents the truth. In reality, we can see the merits of both systems, and which one is more valuable to the consumer is largely a matter of personal perception.
To this day Intel still provides processor TDP (thermal design power) specifications with a single purpose in mind - ensuring thermal engineers have the information they need to do their jobs. Intel knows companies providing platforms based on their products must be able to design and manufacture cooling solutions capable of dissipating the installed processor's maximum heat production - all without violating temperature limits. Designing around these worst-case values ensures the system remains stable under all computing conditions.
AMD's focus is very different, as they have decided to use this data as a marketing tool. By drawing attention to the processor APC (average power consumption), they hope to appeal to businesses looking to lower costs associated with their data infrastructure's operation. Although most end users find little reason to concern themselves with the relatively small monthly savings that can come from a single system's lowered power consumption, this can be a significant sum of money for corporations supporting hundreds or even thousands of workstations. Then again, any business supporting thousands of computers usually has other concerns. Do they worry more about the $5,000-$10,000 per month (or more) spent on the employee using a workstation, or the $10-$30 spent on the power for the workstation? The greater concern is often whether or not a given location has the capacity to power the workstations, not how much the power will cost.
With that said, we would argue that AMD is pandering to the public while Intel has chosen to support the industry developers. We can all certainly agree though: no matter which method you believe is more correct, quoted numbers are useless without a consistent means for calculation.
Surprisingly, Intel has chosen to leave the QX9650's TDP unchanged from the 65nm QX6850's given value of 130W. This is a little confusing as reports from Intel on 45nm process technology improvements provide us with claims of switching energy efficiency increases of up to 30% and a reduction in transistor gate leakages of 10x or more. Could basic core performance improvements such as the incorporation of the new SSE4 instruction set have made such a difference in overall CPU efficiency? We think not. Obviously, there is something more going on here; either the QX6850 TDP is vastly under-rated or the QX9650 is much better than suggested. Perhaps over-rating the QX9650's TDP gives Intel the option in claiming further thermal improvements later. We will share the method we used in calculating a more representative TDP rating for our 45nm quad-core in a moment, but we found the value to be closer to 100W - some 30W less than the figure provided by the blue team, and right in line with the 30% energy efficiency increase.
Determining just how much power a particular processor consumes at a given operating frequency is more difficult than one might originally think. A few different methods exist for estimating these values - one requires nothing more that the processor's specified TDP and then scales this value based on a given overclocked core frequency and voltage. This isn't going to cut it for us, especially considering this technique insists we place full faith in Intel's quoted QX9650 TDP, a number we know to be sometimes unrepresentative of actual operating conditions. Instead, we decided to get creative and develop our own method. The concept is rather simple: we will measure the power draw from the wall, subtract off power consumption for "static" components, correct for PSU efficiency, and then devise a means for determining what portion of the remaining power the CPU consumes - by somehow attributing the remainder to "everything else." The biggest challenge will be devising a means for accurately determining where to place this final split.
Choosing the right PSU is vital in the success of our mission, and employing the services of a Corsair unit means we can take advantage of the published efficiency curves. Monitoring and recording total system power draw is easy thanks to our Kill-A-Watt from P3 International. Finally, calculating just how much power is used by static loads (fans, pumps, HDDs, etc.) won't be too hard at all - simply noting the power draw before and after disconnecting the load is quick and effective. Indeed, developing a method for subtracting off power consumed by the motherboard, memory, and graphics card is going to require the most thought.
Our approach is rather unique: we vary CPU frequency and voltage and then plot the base system load delta versus frequency. System load delta is the difference between wall power minus static loads at CPU full load and wall power minus static loads at idle - both corrected for PSU efficiency. Graphing the delta means that the plotted power varies solely as a function of CPU speed. Our immediate results generate the following graph.
Base System Power Delta (W) versus Processor Frequency (GHz)
Extending the curve downwards allows us to extrapolate our plot's predicted y-intercept. Mathematically, this point represents the frequency in which CPU full load power minus idle power is zero (CPU idle power equals CPU full power). Logic suggests that as the CPU full load power approaches zero so will idle power, especially considering idle power should always be less than the full load power. Without much argument, we find ourselves accepting this as our CPU minimum energy frequency (about 240MHz).
We then plot the base system idle power (wall power minus static loads at idle, again corrected for PSU efficiency) versus the same set of frequencies. Creating a best-fit equation and solving for power using the minimum energy frequency found in the previous graph above gives us the base system power consumption with the CPU at its minimum energy (near zero). This is as close we are going to come to quantitatively determining the idle power consumption of the motherboard, memory, and graphics card combined. We calculated a value of 110W using an ASUS P5E3, 4GB of OCZ DDR3, and a single 8800 Ultra resting comfortably at 500Mhz on a 2D desktop. More likely than not the power-hungry GPU and overclocked X38 chipset make up the lion's share of this value.
With this number our goal is in sight - subtracting this value from the corrected base system idle values used in the creation of our second graph (not shown) gives us the CPU idle power points. Adding to these the base system load deltas plotted in the figure above provides us with the final unknowns - actual CPU full load power values. Joining these two sets of data points gives us the data below.
This graph rewards our hard work by providing us with a wealth of knowledge. Although the values above are highly precise only when referring to our particular QX9650 (every CPU is a little different), the accuracy of our method should be very good. The first thing we notice is how full load power consumption quickly increases to almost uncontrollable levels when pushing above ~4.25GHz. In fact, we found achieving true stability any higher nearly impossible with water-cooling alone. Users who are familiar with overclocking will recognize this trend: a CPU usually scales extremely well up to a certain point, beyond which any further overclocking requires an excessive amount of additional voltage. This is normal and exactly where this point lies is a function of cooling and silicon limits (i.e. process technology) and in reality has very little to do with luck.
An example of the findings that can be developed by measuring system response
We made this last graph using our CPU full load power consumption/frequency pair data points from the figure above. Based on our examinations, just about every Core 2 Extreme QX9650 owner should have little trouble accomplishing at least a 3.9GHz overclock. Upgrading the cooling used will at best provide modest improvements as these quad-cores begin to generate a lot of heat when pushed much further.
56 Comments
View All Comments
Aivas47a - Wednesday, December 19, 2007 - link
Great article. You guys have really been distinguishing yourselves with in-depth work on overclocking the last few months: exploring obscure bios settings, tinkering with "extreme" cooling -- keep it up!My experience with a qx9650 so far is very similar to yours: easy scaling to 4 ghz, difficult scaling after that with 4.2 ghz being the practical max for regular operation (folding, etc.).
One issue I will be interested to see you address in the future is fsb overclocking on yorkfield. So far I am seeing yorkfield top out at lower fsb (450-460) than was possible for kentsfield on a comparable P35 or X38 platform. That is not so significant for the unlocked Extreme Edition chips, but could make it difficult to achieve the magic 4 ghz with the q9550 and especially the q9450.
Aivas47a - Wednesday, December 19, 2007 - link
Great article. You guys have really been distinguishing yourselves with in-depth work on overclocking the last few months: exploring obscure bios settings, tinkering with "extreme" cooling -- keep it up!My experience with a qx9650 so far is very similar to yours: easy scaling to 4 ghz, difficult scaling after that with 4.2 ghz being the practical max for regular operation (folding, etc.).
One issue I will be interested to see you address in the future is fsb overclocking on yorkfield. So far I am seeing yorkfield top out at lower fsb (450-460) than was possible for kentsfield on a comparable P35 or X38 platform. That is not so significant for the unlocked Extreme Edition chips, but could make it difficult to achieve the magic 4 ghz with the q9550 and especially the q9450.
Doormat - Wednesday, December 19, 2007 - link
Though its somewhat disappointing on the rumors that Intel has postponed the launch of their QuadCore desktop chips from January to March.Sunrise089 - Wednesday, December 19, 2007 - link
I agree with everyone else - really top notch stuff here.1 glaring typo though, from the first page: "Moving to a smaller node process technology allows for the potential of one or two things to happen. " - the "or" should be an "of"
ChronoReverse - Wednesday, December 19, 2007 - link
It seems that ATI cards have less of a drop going from XP to Vista (down to zero and even negative sometimes). It might be instructive to use that for the charts that compare Vista to XP for 3D (e.g., the 3Dmark06 benchmark).melgross - Wednesday, December 19, 2007 - link
Capacitors have their capacitance turned into reactance at higher frequencies. Anything that qualifies, in a circuit, as a capacitor, such as two wires riding in parallel, will have, to a greater or lesser extent, the same problem in the design.Reactance rolls off high frequencies. More power is required to offset that.
This is the same problem whether dealing with low frequencies in an audio circuit (where it may be less of a problem), or a high performing computer. It's almost impossible to eliminate all stray capacitance from a circuit, and more circuitry becomes capacitive at higher frequencies. This will only increase as a problem as we get to smaller processes, such as 32nm.
andyleung - Wednesday, December 19, 2007 - link
I am very interested in the performance of these new CPUs. They are Quad-Core and they are good enough to perform some heavy duty business tasks. Wondering how they work with JEE performance.BLHealthy4life - Wednesday, December 19, 2007 - link
This article is a perfect example of what makes Anandtech so great. Anandtech has the most brilliant and most technically savvy guys on the internet.Very rarely will you fine any other website review pieces of hardware with such intricate detail for hardware specs and the technology behind it.
Great work guys!
BL
kkak52 - Wednesday, December 19, 2007 - link
really an informative article.... good work!Bozo Galora - Wednesday, December 19, 2007 - link
A 10+ article, especially the vdroop section.Its nice to see something on AT like the old days thats cuts through the BS and actually gives real usable info.
Quite a tour de force.
Nice work.