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

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


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

chromium-rel-mac11-air

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

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

Bisect Details
  Configuration: mac_air_perf_bisect
  Benchmark    : system_health.common_desktop
  Metric       : timeToFirstPaint_avg/load_search/load_search_yandex

Revision             Result                  N
chromium@492267      228.937 +- 420.292      21      good
chromium@492878      202.186 +- 216.704      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=load.search.yandex system_health.common_desktop

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

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


For feedback, file a bug with component Speed>Bisection

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/148672d9780000

Kicked off a pinpoint bisect.

📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/148672d9780000

Too noisy to repro :(