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

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


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

chromium-rel-mac11-air

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

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

Bisect Details
  Configuration: mac_air_perf_bisect
  Benchmark    : battor.steady_state
  Metric       : story:power_avg/http___www.slideshare.net_patrickmeenan

Revision             Result                  N
chromium@487828      4.6247 +- 1.60799       21      good
chromium@487924      4.56555 +- 1.18743      20      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=http...www.slideshare.net.patrickmeenan battor.steady_state

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

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


For feedback, file a bug with component Speed>Bisection

By eye both ref and actual look to be trending gradually up. Given no bisect going to close as WontFix.