[Q] CPU throttle won't work in surface pro?

Search This thread

theboundless

Member
Jul 5, 2010
49
1
In the power options, under processor power management, the maximum processor state on battery seems to always revert back to 100% after a reboot or changing power plans. Any ideas why the setting won't stick?
 

mkhalil06

Senior Member
Mar 23, 2011
123
11
I noticed this as well
..very annoying

is that the only setting you noticed reverting? or are there more?
 

Ryno_666

Senior Member
Aug 25, 2009
934
312
I assumed win8 handles processes differently requiring less battery consumption.

Sent from my EVO using xda premium
 

mkhalil06

Senior Member
Mar 23, 2011
123
11
but that isn't the issue

if u go into settings and change the 100% to anything else
it always reverts back .....very annoying ....marked difference in battery life noticed
 

LastBattle

Senior Member
May 27, 2012
57
2
Did anyone try 20% CPU so far ? And if so, how is the battery life?
I won't mind getting Surface Pro if I can throttle down its CPU when on battery to Surface RT's speed for a longer battery.

I currently have a RT version with me :D
 

GoodDayToDie

Inactive Recognized Developer
Jan 20, 2011
6,066
2,933
Seattle
Power consumption curve for CPUs is very non-linear. 90% from 100% will probably save you more power than 20% from 90% will. You'd just be wasting a ton of processing capability.
 

isangelous

Senior Member
Jan 28, 2009
215
26
England
Power consumption curve for CPUs is very non-linear. 90% from 100% will probably save you more power than 20% from 90% will. You'd just be wasting a ton of processing capability.
Not only that but the windows throttle percentage is not really as specific as a 0-100 range would suggest, so even if you set 20% it might limit the cpu to its minimum frequency.
If you use a tool such as this you can see what the current frequency is: http://www.cpuid.com/softwares/tmonitor.html
With my laptops (much slower) Core2Duo the minimum frequency was too slow, but about 50% of the max worked well and dramatically reduced the heat under load.
Some people reckon it is better to allow the cpu to use its full frequency so that it finishes the job faster and can move back to the lowest idle state. I am not sure that really applies to i5 (which doesn't support the ARM-style idle states that haswell will) and like you say the power consumption at lower cpu frequencies doesn't vary much. My experience with windows is that sometimes for no apparent reason at all programs such as word or chrome sit using 50+% of the cpu and you have to restart the process. It doesn't happen often at all but you might not realise until your battery is low. With the pro's i5 I expect you could get away with quite a low cpu frequency and would at least know you will always get roughly the same battery life.
 

Walderstorn

Senior Member
Oct 27, 2009
137
20
This is the same problem that w700 has, an even earlier product. This situation made the biggest thread in the acer community because people are angry, some even took back their products and traded for the surface which made it the same than people realized it was not the w700 itself. Throttle stop didnt work because it seems to be more temp related.

Here are some interesting topics

http://community.acer.com/t5/Acer-T...rottling-Turbo-Boost-issues/td-p/6873/page/28

http://forum.tabletpcreview.com/acer-gateway/54122-w700-throttling.html
 

jhoff80

Senior Member
Apr 8, 2008
221
33
Samsung Galaxy S21 Ultra
This is the same problem that w700 has, an even earlier product. This situation made the biggest thread in the acer community because people are angry, some even took back their products and traded for the surface which made it the same than people realized it was not the w700 itself. Throttle stop didnt work because it seems to be more temp related.

Here are some interesting topics

http://community.acer.com/t5/Acer-T...rottling-Turbo-Boost-issues/td-p/6873/page/28

http://forum.tabletpcreview.com/acer-gateway/54122-w700-throttling.html


Actually, it is nothing like that problem. The OP is talking about manually limiting the max clock of the device using the Windows setting that has been there for a while now.