Telemetry: Pin Nexus 5 cores online. Limit CPU & GPU frequency.

Telemetry: Pin Nexus 5 cores online. Limit CPU & GPU frequency.

The Nexus 5 throttles CPU clock quickly under load, going from 2.27GHz
down to 1.19GHz.  Current Performance Dashboard results show this,
as they tend to ping-pong between best & worst thermal states.

This CL turns on all 4 cores on N5, and limits CPU to 1.19GHz which matches
scaling under high load.

It also limits GPU from 450MHz down to 200Mhz.

BUG=383566
Committed: https://crrev.com/2239cb64943b945fee522d58518e955d237da193
Cr-Commit-Position: refs/heads/master@{#299770}

[vmiura, 2014-10-14 19:47:59]

vmiura@chromium.org changed reviewers:
+ pasko@chromium.org, skyostil@chromium.org

[vmiura, 2014-10-14 19:48:00]

ptal

[vmiura, 2014-10-14 19:53:23]

vmiura@chromium.org changed reviewers:
+ dtu@chromium.org

[dtu, 2014-10-14 23:05:23]

lgtm

[Sami, 2014-10-15 13:29:17]

https://codereview.chromium.org/652343002/diff/1/build/android/pylib/perf/per...
File build/android/pylib/perf/perf_control.py (right):

https://codereview.chromium.org/652343002/diff/1/build/android/pylib/perf/per...
build/android/pylib/perf/perf_control.py:82: }.get(product_model, 'ondemand')
Is this the right choice for Nexus 5? Please make it explicit if so.

https://codereview.chromium.org/652343002/diff/1/build/android/pylib/perf/per...
build/android/pylib/perf/perf_control.py:99: '  test -e $FILE && echo %s >
$FILE\n'
nit: %s should really be a %d here, right?

https://codereview.chromium.org/652343002/diff/1/build/android/pylib/perf/per...
build/android/pylib/perf/perf_control.py:100: 'done\n') % (cpu_cores,
str(value))
Remove str() if you agree with above.

[vmiura, 2014-10-15 20:15:01]

https://codereview.chromium.org/652343002/diff/1/build/android/pylib/perf/per...
File build/android/pylib/perf/perf_control.py (right):

https://codereview.chromium.org/652343002/diff/1/build/android/pylib/perf/per...
build/android/pylib/perf/perf_control.py:82: }.get(product_model, 'ondemand')
On 2014/10/15 13:29:17, Sami wrote:
> Is this the right choice for Nexus 5? Please make it explicit if so.

Done.

https://codereview.chromium.org/652343002/diff/1/build/android/pylib/perf/per...
build/android/pylib/perf/perf_control.py:99: '  test -e $FILE && echo %s >
$FILE\n'
On 2014/10/15 13:29:17, Sami wrote:
> nit: %s should really be a %d here, right?

Done.

https://codereview.chromium.org/652343002/diff/1/build/android/pylib/perf/per...
build/android/pylib/perf/perf_control.py:100: 'done\n') % (cpu_cores,
str(value))
On 2014/10/15 13:29:17, Sami wrote:
> Remove str() if you agree with above.

Done.

[vmiura, 2014-10-15 20:15:07]

The CQ bit was checked by vmiura@chromium.org

[commit-bot: I haz the power, 2014-10-15 20:16:03]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/652343002/20001

[commit-bot: I haz the power, 2014-10-15 21:26:01]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2014-10-15 21:26:40]

Patchset 2 (id:??) landed as
https://crrev.com/2239cb64943b945fee522d58518e955d237da193
Cr-Commit-Position: refs/heads/master@{#299770}

[epennerAtGoogle, 2014-10-16 18:11:38]

epenner@google.com changed reviewers:
+ tonyg@chromium.org

[epennerAtGoogle, 2014-10-16 18:13:06]

+Tony for heads up.

I was out sick. I think this is great but only concern is that this mode is set
for all of Telemetry. Might be good to give a fairly wide heads-up to test
owners.

[rmistry, 2015-01-30 14:48:31]

On 2014/10/16 18:13:06, epennerAtGoogle wrote:
> +Tony for heads up.
> 
> I was out sick. I think this is great but only concern is that this mode is
set
> for all of Telemetry. Might be good to give a fairly wide heads-up to test
> owners.

I know this CL is a few months old but a question for my understanding:
Does this change limit CPU and GPU on N5s for all telemetry benchmarks (i.e.
repaint, rasterize_and_record_micro)?

[vmiura, 2015-01-30 17:16:51]

On 2015/01/30 14:48:31, rmistry wrote:
> On 2014/10/16 18:13:06, epennerAtGoogle wrote:
> > +Tony for heads up.
> > 
> > I was out sick. I think this is great but only concern is that this mode is
> set
> > for all of Telemetry. Might be good to give a fairly wide heads-up to test
> > owners.
> 
> I know this CL is a few months old but a question for my understanding:
> Does this change limit CPU and GPU on N5s for all telemetry benchmarks (i.e.
> repaint, rasterize_and_record_micro)?

Yes, I think all benchmarks currently use SetHighPerfMode().