|
2010-06-30
, 20:08
|
Posts: 1,224 |
Thanked: 1,763 times |
Joined on Jul 2007
|
#4562
|
Clock [MHz]
Time [s] when Pi calculation finished
average current consumption [mA?]
So here it goes:
500
49
556
600
41
560
850
31
609
1000
25
736
My conclusion at the moment though is that a higher clock (even with lowered voltage) isn't necessarily more battery friendly than a lower clock just because it allows the CPU to complete its tasks faster and have more sleep time. This is probably because at higher clocks it consumes so much more power that it's not worth it... anyway I'll also have to check how the CPU behaves at 125MHz and 250MHz... At the moment 600MHz seems to be most effective clock though.
The Following User Says Thank You to Matan For This Useful Post: | ||
|
2010-06-30
, 20:22
|
Posts: 1,224 |
Thanked: 1,763 times |
Joined on Jul 2007
|
#4563
|
Even while playing Music or running a movie, the CPU is not ON all the time. A lot of that is done via the DSP anyways, so your CPU would remain idle a significant amount of time (as an example, play an mp3 and run Conky and you would see that the CPU is usually at 500MHz if you are running ideal). So while the test is valid, the premise isn't. Also, to sample current properly, unfortunately once every second isn't enough. You are talking more like 30 times a second, given how many times the CPU is waking up every second.
The Following User Says Thank You to Matan For This Useful Post: | ||
|
2010-06-30
, 22:15
|
Posts: 145 |
Thanked: 91 times |
Joined on Jun 2010
|
#4564
|
Your data does not support your conclusion:
The CPU took 41*560=22960 units of energy to calculate pi at 600MHz, but only took 25*736=18400 units to do the exact same job at 1000MHz, so was, in fact 20% more power efficient at 1000MHz.
|
2010-06-30
, 22:55
|
Posts: 992 |
Thanked: 995 times |
Joined on Dec 2009
@ California
|
#4565
|
|
2010-07-01
, 07:14
|
Posts: 145 |
Thanked: 91 times |
Joined on Jun 2010
|
#4566
|
|
2010-07-01
, 07:21
|
Posts: 738 |
Thanked: 179 times |
Joined on Mar 2010
@ Gold Coast, Australia
|
#4567
|
|
2010-07-01
, 07:42
|
|
Posts: 324 |
Thanked: 201 times |
Joined on Apr 2010
@ UK
|
#4568
|
Hey guys serious question here, i just overclocked mine to 500 1100 running super fast and fine atm, im look at conky and its jumping from like 700 to 500 to 1100 whats the go here and i just seen 805.... when i was in terminal i just went sudo...
kernel config limits 500 1100 succesfully loaded
is that normal to see it go from 700 to 500 and random like that.. when im pushing it to it stays at 1100
|
2010-07-01
, 07:43
|
Posts: 145 |
Thanked: 91 times |
Joined on Jun 2010
|
#4569
|
Hey guys serious question here, i just overclocked mine to 500 1100 running super fast and fine atm, im look at conky and its jumping from like 700 to 500 to 1100 whats the go here and i just seen 805.... when i was in terminal i just went sudo...
kernel config limits 500 1100 succesfully loaded
is that normal to see it go from 700 to 500 and random like that.. when im pushing it to it stays at 1100
|
2010-07-01
, 07:49
|
Banned |
Posts: 388 |
Thanked: 57 times |
Joined on Mar 2010
|
#4570
|
Thread Tools | |
|
Polling 30 times a second should basically be no problem but I assume that this alone would possibly create too much CPU load and therefore affect the result.
You are right that while playing music, the CPU stays mainly at 500MHz with ideal configuration, which is because CPU load stays usually around 20 - 30 %. But that wasn't necessarily what I was testing for, as I was setting the frequencies to a fixed value to check WHICH frequency is the most efficient in terms of battery consumption. So I don't really get your point. Besides if you check powertop while playing music you'll see that the CPU never gets into its deepest sleep state C3 (which again is slightly offtopic here).