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

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


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

chromium-rel-win7-dual
chromium-rel-win7-gpu-intel

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

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

Bisect Details
  Configuration: winx64intel_perf_bisect
  Benchmark    : v8.runtimestats.browsing_desktop
  Metric       : V8 C++:duration_avg/browse_search/browse_search_google_india

Revision             Result                  N
chromium@490661      50.4455 +- 6.69191      21      good
chromium@490675      50.9859 +- 7.71099      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.india 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/8972183903757473936


For feedback, file a bug with component Speed>Bisection

not reproducible