Re: [11/11] system 1: Saving energy using DVFS
From: Pavel Machek
Date: Mon Jan 20 2014 - 11:33:06 EST
On Tue 2014-01-07 16:19:47, Morten Rasmussen wrote:
> Most modern systems use DVFS to save power by slowing down computation
> throughput when less performance is necessary. The power/performance
> relation is platform specific. Some platforms may have better energy
> savings (energy per instruction) than others at low frequencies.
> To have something to relate to, here is an anonymized example based on
> a modern ARM platform:
And here is anonymized example I pulled out of my hat:
Ammount of anonymization Usefulness of information
Come on, you can surely do better than "trust me, it is modern". Now
we can't verify those numbers. And they don't make sense.
> Performance Energy/instruction
> 1.0 1.0
> 1.3 1.6
> 1.7 1.8
> 2.0 1.9
> 2.3 2.1
> 2.7 2.4
> 3.0 2.7
> Performance is frequency (~instruction issue rate) and
> energy/instruction is the energy cost of executing one (or a fixed
> number of instructions) at that level of performance (frequency). For
> this example, it costs 2.7x more energy per instruction to increase the
> performance from 1.0 to 3.0 (3x). That is, the amount of work
> (instructions) that can be done on one battery charge is reduced by 2.7x
> (~63%) if you run as fast as possible (3.0) compared to running at
> slowest frequency (1.0).
This very heavily depends on what you count to the total energy,
right? And it is very hard to argue with you before you anonymized
Anyway, you assuming modern system, low frequency should be cca
0.5GHz, with high cca 1.5GHz. Do you claim that operation on 1.5GHz
takes 9x the power of 0.5GHz operation?
Do you count DRAM to the power consumption?
> To save energy, the higher frequencies should be avoided and only used
> when the application performance requirements can not be satisfied
> otherwise (e.g. spread tasks across more cpus if possible).
This is in very steep contrast with race-to-idle on the PCs.
> When considering the total system power it may save energy in some
> scenarios by running the cpu faster to allow other power hungry parts of
> the system to be shut down faster. However, this is highly platform and
> application dependent.
Aha. Devil is in the details. "I pulled random numbers out of the hat,
and they are wrong, but they are wrong in platform specific way. And I
anonymized them for you so that you can't verify them".
Can we talk specific machine, please? You are talking Android all the
time, so pick one cellphone you care about, and provide real numbers...
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/