Dynamic OC Software?

[icanhascpu2]

Ive been a BIOS OCer for years, but recently I've wanted to delve into software overclocking and core/thread management. Being certain things only used a limited number of cores, and I can get a better OC if I OC 2 cores instead of all.

I started off using AMD Overdrive, but frankly this thing is a piece of shit. Wrong readings all over the place and really badly done dynamic overclocking that will cuase a bluescreen due to how they handle voltages and OC/UCing. It does have a nice feature where if you open a certain application it will trigger an event and set that application to certain core affinities and whatnot.

I'm wondering if anyone has some beter options for better software that will do this sort of thing

 

[Yuriman]

I assume you're talking about Piledriver?

 

[icanhascpu2]

Using a Phenom II 965BE

 

[icanhascpu2]

*crickets*

 

[PG]

It's not a software problem. Deneb doesn't allow what you want.
Read more here from the Anandtech original Phenom II 940 review in 2009: http://www.anandtech.com/show/2702/6

"Finally, Cool 'n' Quiet You Can Use

Modern day microprocessors have many operating frequencies they can choose from; these are called p-states. The original Phenom only had two p-states: full frequency and 1/2 frequency. A Phenom 9950 2.6GHz would either run at 2.6GHz or 1.3GHz. The original Phenom was the first quad-core x86 CPU to allow each core to operate at an independent p-state. All of Intel's quad-cores at that point required all four cores to run at the same p-state.

In theory, the AMD design made sense. If you were running a single threaded application, the core that your thread was active on would run at full speed, while the remaining three cores would run at a much lower speed. AMD included this functionality under the Cool 'n' Quiet umbrella. In practice however, Phenom's Cool 'n' Quiet was quite flawed. Vista has a nasty habit of bouncing threads around from one core to the next, which could result in the following phenomenon (no pun intended): when running a single-threaded application, the thread would run on a single core which would tell Vista that it needed to run at full speed. Vista would then move the thread to the next core, which was running at half-speed; now the thread is running on a core that's half the speed as the original core it started out on.

Phenom II fixes this by not allowing individual cores to run at clock speeds independently of one another; if one core must run at 3.0GHz, then all four cores will run at 3.0GHz. In practice this is a much better option as you don't run into the situations where Phenom performance is about half what it should be thanks to your applications running on cores that are operating at half speed. "


The later Thuban core Phenom II and the FX series cpus have Turbo that will do what you want and can be customized with AMD Overdrive.

 

[icanhascpu2]

"Phenom II fixes this by not allowing individual cores to run at clock speeds independently of one another; if one core must run at 3.0GHz, then all four cores will run at 3.0GHz. In practice this is a much better option as you don't run into the situations where Phenom performance is about half what it should be thanks to your applications running on cores that are operating at half speed. ".

I'm already running cores at different speeds, so that *is* possible stably.

The problem is doing it dynamically. /sadface