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

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


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

chromium-rel-mac-retina

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

=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: mac_retina_perf_bisect
  Benchmark    : battor.trivial_pages
  Metric       : story:power_avg/TrivialWebGLPageSharedPageState

Revision             Result                   N
chromium@488541      20.4397 +- 0.471067      21      good
chromium@488640      21.0326 +- 4.63182       21      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=TrivialWebGLPageSharedPageState battor.trivial_pages

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

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


For feedback, file a bug with component Speed>Bisection

Ref and actual trending up slowly over time. Given no bisect results closing.