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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgnKPHvAoM


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

chromium-rel-mac-retina

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

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

Bisect Details
  Configuration: mac_retina_perf_bisect
  Benchmark    : v8.runtimestats.browsing_desktop_classic
  Metric       : GC:duration_avg/browse_search/browse_search_google_india

Revision             Result                  N
chromium@458714      10.3981 +- 3.83515      21      good
chromium@458826      9.98067 +- 2.85722      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=browse.search.google.india v8.runtimestats.browsing_desktop_classic

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8983571430185767504

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=6729451993300992


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!