linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Morten Rasmussen <morten.rasmussen@arm.com>
Cc: peterz@infradead.org, mingo@kernel.org, rjw@rjwysocki.net,
	markgross@thegnar.org, vincent.guittot@linaro.org,
	catalin.marinas@arm.com, linux-pm@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [11/11] system 1: Saving energy using DVFS
Date: Mon, 20 Jan 2014 17:32:54 +0100	[thread overview]
Message-ID: <20140120163254.GA23051@amd.pavel.ucw.cz> (raw)
In-Reply-To: <1389111587-5923-12-git-send-email-morten.rasmussen@arm.com>

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      	 
0.0	   			 1.0
0.5				 0.05
1.0				 0.0

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
your numbers.

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...

									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2014-01-20 16:32 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-07 16:19 [0/11][REPOST] Energy-aware scheduling use-cases and scheduler issues Morten Rasmussen
2014-01-07 16:19 ` [1/11] issue 1: Missing power topology information in scheduler Morten Rasmussen
2014-01-07 16:19 ` [2/11] issue 2: Energy-awareness for heterogeneous systems Morten Rasmussen
2014-01-07 16:19 ` [3/11] issue 3: No understanding of potential cpu capacity Morten Rasmussen
2014-01-13 21:07   ` Rafael J. Wysocki
2014-01-14 10:27     ` Peter Zijlstra
2014-01-14 16:39     ` Morten Rasmussen
2014-01-14 16:51       ` Peter Zijlstra
2014-01-07 16:19 ` [4/11] issue 4: Tracking idle states Morten Rasmussen
2014-01-07 16:19 ` [5/11] issue 5: Frequency and uarch invariant task load Morten Rasmussen
2014-01-08 12:31   ` Peter Zijlstra
2014-01-16 11:16     ` Morten Rasmussen
2014-01-07 16:19 ` [6/11] issue 6: Poor and non-deterministic performance on heterogeneous systems Morten Rasmussen
2014-01-07 16:19 ` [7/11] use-case 1: Webbrowsing on Android Morten Rasmussen
2014-01-07 16:19 ` [8/11] use-case 2: Audio playback " Morten Rasmussen
2014-01-07 16:19 ` [9/11] use-case 3: Video " Morten Rasmussen
2014-01-07 16:19 ` [10/11] use-case 4: Game " Morten Rasmussen
2014-01-07 16:19 ` [11/11] system 1: Saving energy using DVFS Morten Rasmussen
2014-01-20 16:32   ` Pavel Machek [this message]
2014-01-21 12:14     ` Morten Rasmussen
2014-01-21 12:31       ` Pavel Machek
2014-01-20 16:49   ` Pavel Machek
2014-01-20 17:10     ` Catalin Marinas
2014-01-20 17:17       ` Catalin Marinas
2014-01-20 17:47         ` Pavel Machek
2014-01-20 18:03           ` Catalin Marinas
2014-01-20 19:15             ` Pavel Machek
2014-01-21 11:19               ` Catalin Marinas
2014-01-20 17:54       ` Pavel Machek
2014-01-20 18:16         ` Catalin Marinas
2014-01-20 20:44           ` Pavel Machek
2014-01-20 18:25         ` Sebastian Reichel
2014-01-21 18:53           ` Kalle Jokiniemi
2014-01-20 18:12       ` Pavel Machek
2014-01-21 11:42         ` Catalin Marinas
2014-01-21 12:20           ` Pavel Machek
  -- strict thread matches above, loose matches on Subject: below --
2013-12-20 16:45 [0/11] Energy-aware scheduling use-cases and scheduler issues Morten Rasmussen
2013-12-20 16:45 ` [11/11] system 1: Saving energy using DVFS Morten Rasmussen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140120163254.GA23051@amd.pavel.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=catalin.marinas@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=markgross@thegnar.org \
    --cc=mingo@kernel.org \
    --cc=morten.rasmussen@arm.com \
    --cc=peterz@infradead.org \
    --cc=rjw@rjwysocki.net \
    --cc=vincent.guittot@linaro.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).