aboutsummaryrefslogtreecommitdiffhomepage
path: root/tools/SkTestScalerContext.h
diff options
context:
space:
mode:
authorGravatar Kevin Lubick <kjlubick@google.com>2017-12-12 15:57:20 -0500
committerGravatar Skia Commit-Bot <skia-commit-bot@chromium.org>2017-12-13 11:38:22 +0000
commite3b013047d002d5749f5fb946df662755dc15232 (patch)
treee99f7d55d9c40706158268127efe08c3b75b4488 /tools/SkTestScalerContext.h
parent1ad55eb2592e8d765863d5a59580a04cbd4876cb (diff)
Experiment with turning CPUs off during perf
Perf was nice and flat after https://skia-review.googlesource.com/c/skia/+/83240 but there was a 4-5x slowdown on the benchmarks themselves, indicating that perhaps we were running nanobench on the LITTLE cores (now on powersave) instead of the big cores we thought (which were recently scaled down). This experiment will show us FOR CERTAIN that we are running on core 0 or 1 which is at .6 max frequency. We expect to see a speedup from the previous results. This is leading to turning of CPUs we don't need to make sure nanobench is running on the ones we expect. Bug: skia: NOTRY=true Change-Id: Ida65181e4d90e778e65e3f22d761288b9ade64f6 Reviewed-on: https://skia-review.googlesource.com/84201 Reviewed-by: Mike Klein <mtklein@chromium.org> Commit-Queue: Kevin Lubick <kjlubick@google.com>
Diffstat (limited to 'tools/SkTestScalerContext.h')
0 files changed, 0 insertions, 0 deletions