- This topic has 4 replies, 4 voices, and was last updated 16 years ago by
.
-
Posts
-
HI:)
Bios/Advanced/CPU Power Saving Mode – enabled [default]
‘disabled’ – Bios commentary says – will decrease system battery life but response time is slightly faster than ‘enabled’
My questions are
1. how the ‘disabled’ works [CPU speed or something]?
2 .is this feature associated with Samsung Speed Manager [Fn+F8]?
3. do you use it, worthy?Thanks for such great forum.
I tried it out of curiosity, and can’t say it made any real difference in terms of responsiveness OR battery life. I ended up returning it to the default. However, I’d be interested in knowing more about this ‘feature’ too.
Cavgirl,
I have had similar observations.
But I don’t have Samsung Battery Manager, maybe that is a reason [besides, I have only Easy Display Manager & Magic Keyboard from Samsung software]I’m not sure, but I think it disables the speedstep (scaling down of the CPU when not fully stressed), which saves some (not extremely much) power if your CPU is idle. On the other hand not saving the power will save you fractions of a second when the cpu goes from idle to stressed (because it is already at max speed, instead of having to be regulated to max speed while being stressed). On this model I’d say it’s better to save battery (unless you’re nearly never unplugged).
From the battery test results at http://www.umpcfever.com/news/?postid=1623 (for the NC10), it appears that under light load that enabling the CPU Power Saving Mode improves battery life by about 2.8% (10 mins); however, under heavy workload the opposite is true, disabling it improves battery life by about 4.9% (14 mins).
Since I want to maximize battery life under heavy load (which I’m assuming is anything when CPU load is > 25%, like when playing a movie), I’ve disabled the CPU Power Saving Mode (Press F2 while starting up to access BIOS). In my case, I did notice better system response with the CPU Power Saving Mode disabled (as indicated by windows opening faster etc).
- You must be logged in to reply to this topic.