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

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


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

android-nexus5X

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

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

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : system_health.common_mobile
  Metric       : timeToFirstMeaningfulPaint_avg/load_search/load_search_ebay

Revision             Result                  N
chromium@490022      459.799 +- 94.8947      21      good
chromium@490131      448.447 +- 109.227      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=load.search.ebay 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/8972207517359711104


For feedback, file a bug with component Speed>Bisection

I'm not convinced there's a regression here.  The ref still seems very close to the metric.