- Dec 30, 2004
- 12,553
- 2
- 76
I can't for the life of me get my 8310 CPU to turbo more than 3.7ghz. Sometimes 4.3ghz pops up, but only rarely.
I just thought there would be some rhyme or reason to the turbo, such as something really simple and common sense that I can think of myself, like
Does anyone know any details about the module loading, scheduling, turboing?
Maybe I could go write a Linux hotplugging driver, that would probably make me better. Could I write a driver like PhenomMSRTweaker to handle it?
I can get around to overclocking, but if a proper turbo implementation would be sufficient.
original thread content
I just thought there would be some rhyme or reason to the turbo, such as something really simple and common sense that I can think of myself, like
- if CPU thermal temp is low, aggressively turbo modules
- if one core is heavily (over 95%) utilized, turbo that module to 4.3ghz
- see if you can fit all other processes on that module's 2nd core
- power gate/shut off other modules not in use
- if module utilization crosses 80%, fire up another module
- unless of course, a program requests separate modules
- if user requests "performance mode", load one core on each module first (0,2,4,6) before loading the second cores of module (1,3,5,7)
- some way to detect light to moderate usage (web browsing), vs gaming-- and try to keep the CPU at as low a frequency and voltage state as possible and just make use of threads to distribute the load to maintain responsiveness
- last of all, stay within 95w
Does anyone know any details about the module loading, scheduling, turboing?
Maybe I could go write a Linux hotplugging driver, that would probably make me better. Could I write a driver like PhenomMSRTweaker to handle it?
I can get around to overclocking, but if a proper turbo implementation would be sufficient.
original thread content
Intel has a piece of software, but if I recall AMD doesn't have a driver to move the frequency-bound process to the turbo'd cores.
For example, if you have one Chrome tab that's currently rendering something, it should go on a Turbo'd core/module, and all the other non-critical system processes should go other modules.
Last edited:
