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

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


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

chromium-rel-win7-x64-dual

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

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

Bisect Details
  Configuration: win_x64_perf_bisect
  Benchmark    : v8.runtimestats.browsing_desktop
  Metric       : Parse-Background:duration_avg/browse_media/browse_media_pinterest

Revision             Result                  N
chromium@508956      477.063 +- 299.923      21      good
chromium@508958      469.221 +- 310.873      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.media.pinterest 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/8965488512556903904


For feedback, file a bug with component Speed>Bisection

not reproducible