After reading multiple articles on various site regarding how the
processor power management works in Vista, I have yet to find a
resolution to my current situation.
I am running Vista Home Premium 32bit on my HP Pavilion tx 2110 with an
AMD X2 Mobile Tech TL-62 2.1Ghz and 3gb of RAM.
Whenever my laptop is unplugged from the wall and running on the
battery, Vista seems to limit the processor frequency to 38% of the max
(roughly 800mhz) no mater the power plan or processor load. While the
computer is plugged in however, everything runs beautifully with the
frequency at 100%.
Here is what the Resource Manager has to say about this:
[image:
http://i238.photobucket.com/albums/f...?t=1237840864]
The CPU graph on the left side is while the computer is plugged in, I
believe I was reading some of the power management articles. The right
side is after the power cord is removed, the spikes are when I was
rendering a small fractal just to push the processor past idling.
Current power plan looks like this:
[image:
http://i238.photobucket.com/albums/f...?t=1237841039]
This is the default High Performance plan. Now from my understanding,
while plugged in this should "force" the processor to maintain a 100%
frequency regardless of the load while unplugging the cord should allow
the cores to float anywhere between 5% and 100% load dependent, although
this remains at 38% consistently.
What I would like it to do is whenever it is unplugged, it should
retain either the 100% stable cap, or be allowed to range so that at
high utilization the frequency may be allowed to range. Through messing
with the "Minimum processor state" and "Maximum processor state" I have
found that the 38% limit does not ever change, even if both setting are
set to 15% or 100%, the while plugged in option however functions as it
should, if I move the upper and lower limits it will mirror this change
both in performance and in the resource manager.
Any suggestions on how to force my plan settings to take effect? Or is
there a way to disable the power management and completely disallow
processor states?
--
luftwaffle