[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: [PATCH] powerdevil-remove-cpufreq.patch
From:       Valerio Pilo <valerio () kmess ! org>
Date:       2010-03-08 12:50:19
Message-ID: 201003081350.20243.valerio () kmess ! org
[Download RAW message or body]

In data luned́ 8 marzo 2010 12:22:17, Holger Macht ha scritto:
: > On 03/08/2010 10:30 AM, Valerio Pilo wrote:
> > In data domenica 7 marzo 2010 23:57:37, Holger Macht ha scritto:
> > : > Remove all CPU frequency scaling code from powerdevil and the kcm
> >> 
> >> module. You should never offer those options to the user because he
> >> might not understand what the impact is. You only want a dynamic
> >> frequency algorithm which is the default these days (ondemand
> >> governor). A good explanation is provided in [1].
> >> 
> >> Regards,
> >> 
> >>  Holger
> > 
> > I disagree too. As Oswald Buddenhagen noted, some applications bog down
> > the CPU, and having the option to switch it to 'powersave' mode is a
> > great way to avoid both heating and battery draining in many situations.
> > (I personally use it a lot, by forcing my laptop into Extreme Powersave
> > mode) [btw, that's in fact "Xtreme Powersave", duh.. That power profile
> > label should be renamed..]
> 
> It's a misunderstanding that you reduce energy consumption by setting
> your processor's governor to 'powersave', really.
> 
> Do you have numbers that you're battery lasts longer than before?
> 
> Regards,
>  Holger

Yes, it lasts longer. Not an amazing amount of time more, but still quite a 
bit longer than when I put it into 'ondemand' and do usual work (web 
development and/or compiling stuff). This is keeping in mind screen brightness 
etc.
I think it happens because when in 'powersave' mode, it can never run at full 
speed...


-- 
Valerio Pilo
KMess developer team
------
KMess
- the Live Messenger alternative for KDE -
web: www.kmess.org - irc: #kmess at Freenode
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

[prev in list] [next in list] [prev in thread] [next in thread]