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

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


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

chromium-rel-win7-gpu-intel

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

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

Bisect Details
  Configuration: winx64intel_perf_bisect
  Benchmark    : v8.runtimestats.browsing_desktop
  Metric       : V8-Only:duration_avg/browse_search/browse_search_google

Revision             Result                 N
chromium@510723      919.38 +- 156.171      21      good
chromium@510764      920.114 +- 129.24      21      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.search.google v8.runtimestats.browsing_desktop

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

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


For feedback, file a bug with component Speed>Bisection