tree 031e10d72da5f9b2d16f81655558251efeb4deb0
parent 964721192150677dc9b0811780841d7b18d07d5f
author Geoffrey Martin-Noble <gcmn@google.com> 1637703140 -0800
committer GitHub <noreply@github.com> 1637703140 -0500
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJhnV3kCRBK7hj4Ov3rIwAAP+4IAAtZN8RMmqn22SfIVRB/3jme
 OWljzdVlvzACY0k2iTH0BUUFJ7HATn7TMBEfrGUZCe9e0CFJ/tpg18fbdAWr4Mcp
 OWYnDuT9QFh4bslx3yDGHoAYClrP5bYOoEqSbbabwvGSUfsYFB9WRd63WjtJbejT
 5zDDocTQP83PiquUDEa7H52/INF4iOU8hV4SvMN1mYFzBVBtAd0w6/2jiPFOiAU7
 BMTOp2FohgEeF3+STLF8qC0TkUcxmUfEyt2Q5LPsnekFMC2Jmd+Tq3H7AVowIPAv
 G5f+nV7M+3aTGeVQ277v9vTwpzav8i4fZwBCWWg253WAqttqI9g4t939QWsWm/k=
 =IsAe
 -----END PGP SIGNATURE-----
 

Set CPUs to max frequency before running benchmarks (#7728)

The aim is that this will reduce variance in benchmarks. Notably, this
reduces our ability to capture important real-world scenarios, like
running across threads with different clock speeds. We are deliberately
making a tradeoff right now to get variance under control and we may
revisit this in the future. Pinning to max clock speed is safe and
consistent only because the benchmark phones are on cooling plates so
thermal throttling won't be a problem.

Only the Pixel phone is pinned because we don't have the Samsung phones
rooted (because Samsung makes this a PITA and doing so caused the phone
to randomly reboot all the time).