All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=762194

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=a7204a6c8ac08eb63edc509dd209be1605a5d10e9c05a553988a5789e7338c12


Bot(s) for this bug's original alert(s):

android-nexus5X
android-nexus7v2
android-one

Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8969256903183868992

=== Auto-CCing suspected CL author altimin@chromium.org ===

Hi altimin@chromium.org, the bisect results pointed to your CL, please take a look at the
results.


=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : Alexander Timin
  Commit : ad368586d08e57b65a6e10af7d07693d89da9f6a
  Date   : Fri Sep 01 13:55:08 2017
  Subject: Reland: [scheduler] Reenable timer throttling for background renderers.

Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : thread_times.key_idle_power_cases
  Metric       : tasks_per_second_total_all/set-timeout.html (Long Idle)
  Change       : 27.84% | 3.59761638914 -> 4.599193675

Revision             Result                    N
chromium@499171      3.59762 +- 0.0578708      6      good
chromium@499179      3.59463 +- 0.0617117      6      good
chromium@499183      3.58093 +- 0.0576999      6      good
chromium@499185      3.59024 +- 0.0990193      6      good
chromium@499186      4.55253 +- 0.0655173      6      bad       <--
chromium@499187      4.59146 +- 0.0748378      6      bad
chromium@499203      4.59919 +- 0.114618       6      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=set.timeout.html..Long.Idle. thread_times.key_idle_power_cases

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8969256903183868992


For feedback, file a bug with component Speed>Bisection

altimin: ping? Looks like this CL regressed the thread_times benchmark.

altimin: is this regression expected? It's pretty consistently above 15% on all android platforms.

This is a measurement side-effect -- there are a small number of internal throttling-related tasks which have been added, but the total time spent in tasks went down.