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

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


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

android-nexus5

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

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

Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : system_health.common_mobile
  Metric       : cpu_time_percentage_avg/browse_media/browse_media_facebook_photos

Revision             Result                     N
chromium@492617      0.641561 +- 0.0357495      21      good
chromium@492792      0.642253 +- 0.0396533      21      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=browse.media.facebook.photos system_health.common_mobile

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

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


For feedback, file a bug with component Speed>Bisection

Looks like a regression due to a CL revert. Closing as wontfix.