Active Topics
-
Is there a section to talk about Java ME? Apps, etc. (5)
to General by teroyk - 1 day, 3 hrs ago -
Extra softwares in Sailfish using CLI, repositories, etc (118)
to SailfishOS by nieldk - 1 day, 8 hrs ago -
Paths (0)
to Maemo 7 / Leste by teroyk - 2 days, 5 hrs ago - more...
elimoon8 |
2009-08-13
, 18:18
|
|
Posts: 122 |
Thanked: 84 times |
Joined on Mar 2009
|
#11
|
If I understand correctly, the performance mode puts the processor constantly at 400 mhz, while "on-demand" lets the processor scale its performance up and down, due to what is required of it and to save battery. If it's not being used, it can operate, say, at 200 mhz and it won't impact use. The "conservative" mode keeps the processor lower than the maximum at all times. The processor is never "overclocked". To keep the device and components safe from overheating, the processors is never forced to go to 600 mhz or 1 ghz.
|
|
2009-08-13
, 18:54
|
|
Posts: 1,213 |
Thanked: 356 times |
Joined on Jan 2008
@ California and Virginia
|
#12
|
The processor never overclocks. It can't go to 600mhz or 1ghz.
Performance: Always at 400mhz
On-demand: Scales between 165mhz and 400mhz
Conservative: Always at 165mhz
Performance mode, AFAIK, was discovered by lcuk when he was making liqbase. The algorithms were so efficient that the tablet would scale down the processor and make the animations jerky. So he found out if you force it to stay at the max, it works a lot better.
Also, I have not found any significant battery savings between the modes, so performance is the best.
Performance: Always at 400mhz
On-demand: Scales between 165mhz and 400mhz
Conservative: Always at 165mhz
Performance mode, AFAIK, was discovered by lcuk when he was making liqbase. The algorithms were so efficient that the tablet would scale down the processor and make the animations jerky. So he found out if you force it to stay at the max, it works a lot better.
Also, I have not found any significant battery savings between the modes, so performance is the best.
__________________
----------------------------------------------------
www.ezschool.com - The best online educational experience.
----------------------------------------------------
www.ezschool.com - The best online educational experience.
|
|
2009-08-13
, 21:33
|
|
Posts: 2,102 |
Thanked: 1,309 times |
Joined on Sep 2006
|
#13
|
The "performance" governor will give worse battery life but probably slightly improved latency than "ondemand". If you wish to modify the CPU scaling from userspace you could always use the "userspace" governor with a suitable daemon to monitor activity and alter the CPU speed.
E.g. http://www.thinkwiki.org/wiki/How_to...caling_Daemons
E.g. http://www.thinkwiki.org/wiki/How_to...caling_Daemons
 |
|
2009-08-13
, 23:42
|
|
Posts: 5,478 |
Thanked: 5,222 times |
Joined on Jan 2006
@ St. Petersburg, FL
|
#14
|
Originally Posted by lardman
Not to overcomplicated things, but there are a number of situations where performance can actually provide slightly better battery life.
The "performance" governor will give worse battery life but probably slightly improved latency than "ondemand".
__________________
Ryan Abel
Ryan Abel
 |
|
2009-08-14
, 01:03
|
|
Posts: 304 |
Thanked: 233 times |
Joined on Jul 2009
@ São Paulo, SP, Brasil
|
#15
|
Originally Posted by GeneralAntilles
And how is that?
Not to overcomplicated things, but there are a number of situations where performance can actually provide slightly better battery life.
(BTW, when we say 'battery life' are we talking about the time it would take to discharge the abttery befre recharging, or the actual life of the battey in the long run, i.e. years before it can't take much charge anymore?)
 |
|
2009-08-14
, 01:11
|
|
Posts: 733 |
Thanked: 991 times |
Joined on Dec 2008
|
#16
|
Originally Posted by nwerneck
Probably because the CPU running at its highest speed can finish a task sooner and then go to idle.
And how is that?
(BTW, when we say 'battery life' are we talking about the time it would take to discharge the abttery befre recharging, or the actual life of the battey in the long run, i.e. years before it can't take much charge anymore?)
| The Following 3 Users Say Thank You to mrojas For This Useful Post: | ||
|
|
2009-08-14
, 01:58
|
|
Posts: 5,478 |
Thanked: 5,222 times |
Joined on Jan 2006
@ St. Petersburg, FL
|
#17
|
Originally Posted by nwerneck
How many hours of charge it gives you.
(BTW, when we say 'battery life' are we talking about the time it would take to discharge the abttery befre recharging, or the actual life of the battey in the long run, i.e. years before it can't take much charge anymore?)
Originally Posted by mrojas
Basically (race-to-idle). The problem with performance is when tasks are sitting around using CPU all day long (even at 0.1%). Then the CPU sits on all that time at a much higher voltage than it would in ondemand.
Probably because the CPU running at its highest speed can finish a task sooner and then go to idle.
If you don't have any tasks using CPU frequently, however, the CPU will actually spend less time active in performance than ondemand.
__________________
Ryan Abel
Ryan Abel
| The Following User Says Thank You to GeneralAntilles For This Useful Post: | ||
|
|
2009-08-14
, 08:32
|
|
Posts: 2,102 |
Thanked: 1,309 times |
Joined on Sep 2006
|
#18
|
Hmm, I understand the reasoning, but is this actually true for our devices?
We'd need to know the power consumption at the different CPU freqs and once the clock has stopped due to the dyntick stuff too, and then decide what usage scenario is most applicable, I don't suppose anyone has that info lying about?
We'd need to know the power consumption at the different CPU freqs and once the clock has stopped due to the dyntick stuff too, and then decide what usage scenario is most applicable, I don't suppose anyone has that info lying about?
|
|
2009-08-14
, 12:34
|
|
Posts: 5,478 |
Thanked: 5,222 times |
Joined on Jan 2006
@ St. Petersburg, FL
|
#19
|
Originally Posted by lardman
Yes.
Hmm, I understand the reasoning, but is this actually true for our devices?
Originally Posted by lardman
I don't have exact numbers on the consumption handy, but there definitely is a large difference.
We'd need to know the power consumption at the different CPU freqs and once the clock has stopped due to the dyntick stuff too, and then decide what usage scenario is most applicable, I don't suppose anyone has that info lying about?
__________________
Ryan Abel
Ryan Abel
| The Following User Says Thank You to GeneralAntilles For This Useful Post: | ||
|
|
2009-08-14
, 14:27
|
|
Posts: 102 |
Thanked: 16 times |
Joined on Sep 2006
@ Manchester
|
#20
|
you will save power by letting the run fast, to get a job done, and then it can drop to a low power idle mode. search "matthew garrett power management" for some good blog posts and videos.
i imagine this is even more true on an arm cpu (compared to desktop/laptop cpus), as it have very low power idle modes.
if you have things running in the background using cpu, they are either along the lines of
* sleep for n milliseconds/seconds/minutes, do something, sleep again
* run as fast as possible all the time
the first case, the soon the job can finish, the sooner you can save power again.
the second case will drain your battery pretty quick no matter what you do.
has anyone tried running powertop on an IT
i imagine this is even more true on an arm cpu (compared to desktop/laptop cpus), as it have very low power idle modes.
if you have things running in the background using cpu, they are either along the lines of
* sleep for n milliseconds/seconds/minutes, do something, sleep again
* run as fast as possible all the time
the first case, the soon the job can finish, the sooner you can save power again.
the second case will drain your battery pretty quick no matter what you do.
has anyone tried running powertop on an IT
__________________
put wikipedia on you 770 or n800
put wikipedia on you 770 or n800
 |
| Tags |
| cpu, mhz, performance |
«
Previous Thread
|
Next Thread
»
|
All times are GMT. The time now is 17:10.