g-p-m always try to set the main policy to 'ondemand'

If we have our AC plugged we would like to use the max performance of our laptop, here' s a very simple patch.

Thanks for your report, confirming, same issue here. An Ubuntu dev should take a look at the patch, thanks you Eduardo!

I like my laptop to not run at full speed (ie full temperature) when it's just sitting on the desk not being used.
ondemand brings in the performance when it is needed, so why change the default?
(also note that this is a gconf setting, so you can choose to override the default as you wish)

 I got your point but if we're talking about "Linux for human beings"
I don't think that gconf is a solution, old linux users know how to
fix it or give an special option, but would be good make the things a
bit easy for the other ones... not all laptops are so faster...

Ed.-

On Fri, Mar 7, 2008 at 8:54 AM, Chris Jones <email address hidden> wrote:
> I like my laptop to not run at full speed (ie full temperature) when it's just sitting on the desk not being used.
> ondemand brings in the performance when it is needed, so why change the default?
> (also note that this is a gconf setting, so you can choose to override the default as you wish)
>
>
>
> --
> g-p-m always try to set the main policy to 'ondemand'
> https://bugs.launchpad.net/bugs/152808
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Hi

Eduardo Silva wrote:
> I got your point but if we're talking about "Linux for human beings"
> I don't think that gconf is a solution, old linux users know how to

I think leaving it at "ondemand" is the solution. It will switch to full
performance when the system is busy, so users will get the performance
they expect from their hardware. Anyone who actually wants to change it
will already know what cpu scaling is and won't be scared of gconf, surely?

> fix it or give an special option, but would be good make the things a
> bit easy for the other ones... not all laptops are so faster...

my laptop is a 1.2ghz pentium m, so it's hardly the fastest thing in the
world, but I don't think there would be any benefit to not using
ondemand. It's not going to make the thing noticeably faster.
Can you demonstrate otherwise?

--
Chris Jones

> I think leaving it at "ondemand" is the solution. It will switch to full
> performance when the system is busy, so users will get the performance
> they expect from their hardware. Anyone who actually wants to change it
> will already know what cpu scaling is and won't be scared of gconf, surely?

I agree with that, my point is about people that don't know about cpu scaling...

> my laptop is a 1.2ghz pentium m, so it's hardly the fastest thing in the
> world, but I don't think there would be any benefit to not using
> ondemand. It's not going to make the thing noticeably faster.
> Can you demonstrate otherwise?

I open this bug because I feel that ondemand doesn't works as well as
I would like, it makes me feel my laptop a little slower... your
laptop is working properly, that's not my case... maybe will be useful
some feedback from another users. Here we have two points of view for
two different cases/machines... Maybe my problem is an isolated one,
maybe not... is there any forum where we can talk about this ?, more
opinions would be very useful.

Ed.-

>
> --
> Chris Jones
>
> --
>
>
> g-p-m always try to set the main policy to 'ondemand'
> https://bugs.launchpad.net/bugs/152808
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Another comments:

if the computer is on the desk and don't being used, is the CPU being
used? , is there any big difference between ondemand and performance
on that case?

IIRC CPU scaling helps to save the battery life on the laptop cases,
but if I'm plugged to AC I would like to have my laptop working as
fast as possible. Final user needs to feel their laptop faster as they
want, this makes sense to me:

case 1: laptop plugged (AC) = use performance (we don't need to save anything)
case 2: laptop using battery as power resource = use ondemand

let's ask to the users... this is not a problem for geeks...

On Fri, Mar 7, 2008 at 10:05 AM, Eduardo Silva <email address hidden> wrote:
> > I think leaving it at "ondemand" is the solution. It will switch to full
> > performance when the system is busy, so users will get the performance
> > they expect from their hardware. Anyone who actually wants to change it
> > will already know what cpu scaling is and won't be scared of gconf, surely?
>
> I agree with that, my point is about people that don't know about cpu scaling...
>
>
> > my laptop is a 1.2ghz pentium m, so it's hardly the fastest thing in the
> > world, but I don't think there would be any benefit to not using
> > ondemand. It's not going to make the thing noticeably faster.
> > Can you demonstrate otherwise?
>
> I open this bug because I feel that ondemand doesn't works as well as
> I would like, it makes me feel my laptop a little slower... your
> laptop is working properly, that's not my case... maybe will be useful
> some feedback from another users. Here we have two points of view for
> two different cases/machines... Maybe my problem is an isolated one,
> maybe not... is there any forum where we can talk about this ?, more
> opinions would be very useful.
>
> Ed.-
>
> >
> > --
>
>
> > Chris Jones
> >
> > --
> >
> >
> > g-p-m always try to set the main policy to 'ondemand'
> > https://bugs.launchpad.net/bugs/152808
> > You received this bug notification because you are a direct subscriber
> > of the bug.
> >
>

Hi

Eduardo Silva wrote:
> I agree with that, my point is about people that don't know about cpu
> scaling...

If they don't know about it, they won't care about it because ondemand
will make their CPU fast when they need it.

> I open this bug because I feel that ondemand doesn't works as well as
> I would like, it makes me feel my laptop a little slower... your

Where are the numbers to prove the overhead of ondemand?

> laptop is working properly, that's not my case... maybe will be useful

That suggests there may be a bug with ondemand for your hardware perhaps.

> maybe not... is there any forum where we can talk about this ?, more
> opinions would be very useful.

I think more facts would be useful :)

--
Chris Jones

> If they don't know about it, they won't care about it because ondemand
> will make their CPU fast when they need it.

If they bought a 2.0GHz CPU laptop, ondemand just will going to scale
to 2.0 as were necessary, if I'm opening openoffice or something
similar, are u sure that ondemand will switch to 2.0 or 1.6 ? , why
the user need to experience a slower machine if he's connected to AC ?

Ondemand is a good solution for a lot of situations, here we're
talking about the 'Laptop connected to AC' case..

>
>
> > I open this bug because I feel that ondemand doesn't works as well as
> > I would like, it makes me feel my laptop a little slower... your
>
> Where are the numbers to prove the overhead of ondemand?

good question, but is not necessary to spent some time to get numbers
to see that our machines are a little slower with ondemand.

> I think more facts would be useful :)

It doesn't make sence to me to set a slower CPU when the laptop is
plugged, ondemand is very helpful but my point is performance.

I'm just proposing to change the AC policy from ondemand to
performance. Plug your laptop to AC and do some test using ondemand
v/s performance, which one is more faster ?, which one gives the best
user experience ?.

Eduardo.

Is there any progress here? or the bug needs to be reassigned? Thanks all.

This should not be a low priority bug. It contributes to the headlines that Ubuntu has a worse battery life than windows. Netbook users who need battery life want to turn powersave on.

The problem is that /etc/init.d/ondemand will after 60 seconds of booting change the frequency scaler to ondemand. This one size fits all is terrible. It should set the frequency scaler to whatever it was set to at last shutdown. If you want performance, it should stay on performance. If you need battery life, it should stay on powersave.

At the moment, even if you change to powersave at login, after 60 seconds from boot, it will switch back to on demand. This is very annoying. The simple solution is to check the frequency scaler policy at shutdown. Save it. On boot performance should be selected until log in when the saved policy should be reinvoked.

This has nothing to do with gnome-power-manager - it doesn't do anything with the governor any more.

In addition to that, changing the governor doesn't really give you any gains anyway. Setting the governor to "powersave" just means your processor takes longer to do the work it needs to do, and doesn't spend as much time as it normally would in the lower power C-states.

Can somebody help me with this bug under which package it should be reassigned? Thank you!

[Expired for Ubuntu because there has been no activity for 60 days.]