Sign in with
Sign up | Sign in

PowerTune With Boost: Is The Accelerator Stuck?

AMD Radeon HD 7970 GHz Edition Review: Give Me Back That Crown!
By , Igor Wallossek

With a basic understanding of what PowerTune with Boost is, we wanted to explore its behavior in more depth.

According to AMD, the Radeon HD 7970 GHz Edition’s base clock is no longer end-user editable. It’s stuck at 1 GHz. When you move the slider in the Catalyst Control Center’s Overdrive tab, you’re actually moving what the company calls a boost state. And because the boost state is accompanied by a higher voltage, overclocking potential should be higher than modifying the base clock. From there, you’re supposed to be able to push Overdrive’s power control slider up even further to keep the card running at its higher P-state for longer without bouncing off of its protection circuitry and back to 1 GHz.

So, in theory, AMD is introducing an extra P-state, allowing the card to either operate at its base clock or a higher frequency. As long as the card stays within its TDP, it’s able to utilize the high clock, which can be adjusted through the Catalyst Control Center. If TDP is exceeded, the clock reverts to 1 GHz. The idea that AMD’s graphics hardware runs at one speed, selected for its applicability to real-world games, but then drops to another speed if some synthetic workload pushes it over the edge is not new at all. The existing Radeon HD 7970 could already do that. Getting more voltage to help augment a higher boost frequency would be a fresh concept, though.

Per AMD’s suggestion, we started bumping up the clock rate slider in Overdrive, hoping to see a higher voltage that’d help us hold onto a correspondingly higher overclock. What we saw instead was that altering the boost frequency by even 1 MHz up or down prevented the card from dynamically switching back to 1 GHz at all. Instead, the GPU remained at its dialed-in boost speed, temps kept going up, and we shut ‘er down to prevent a more serious problem.

We reproduced this behavior on two cards in two different countries running on four different platforms and multiple installations of Windows. Interestingly, we didn’t even need to adjust the power slider in Overdrive to maintain our overclocked boost state. We simply set a higher frequency, fired up FurMark, and watched the temp crest 90° in under a minute.

Our interest piqued, we decided to follow up by testing the card’s load in a number of scenarios. These included FurMark with boost operating as it should (between 1050 and 1000 MHz), as well as completely pegged at 1051 MHz. Bitmining serves as our compute workload, while the Aliens vs. Predator demo represents gaming. As you can see, several tests remained at full load with the card running at its maximum clock rate.

So, what are we looking at here? A protection mechanism that only works at its default settings, or a power-limiting feature asleep on the job? In order to answer our questions, we’ll look at power draw on the 12 V rail during each load scenario.

The Bitmining client and FurMark, both running at a constant 1051 MHz, pretty much max out the typical board power rating set forth by AMD. When the clock-limiting feature works properly, though, FurMark’s consumption drops notably. AvP and our OpenCL-based test are both able to run at full speed without any need to jump down to a lower frequency.

Now, if we take a look at the currents involved, we can see that at a partial load of less than 70 percent, the OpenCL test demonstrates some interesting spikes. Since the graph for the chip’s power draw, being a product of amperage and voltage, is a lot straighter, we can surmise that the GHz Edition card’s core voltage is constantly rising and falling.

It looks like we end up with a “persistent boost state.” Does that mean we can get by without any throttling thanks to built-in headroom? As of now, we still don’t know why overclocking confounds PowerTune.

We also wondered why only applications like FurMark and OCCT were able to trigger the feature, and only when we left the boost clock at its default value of 1050 MHz. Pure compute-oriented workloads able to generate similar load levels didn’t trigger the same reaction.

Digging deeper still, we’re going back to re-test everything on the original Radeon HD 7970. After all, AMD promises that this new card offers better performance at the same power levels using the same GPU. That’s be great, if it pans out.

React To This Article