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

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


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

chromium-rel-win7-gpu-nvidia

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

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

Bisect Details
  Configuration: winx64nvidia_perf_bisect
  Benchmark    : system_health.common_desktop
  Metric       : cpu_time_percentage_avg/load_media/load_media_9gag

Revision             Result                     N
chromium@490761      0.198064 +- 0.0375844      21      good
chromium@490797      0.196911 +- 0.0343657      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=load.media.9gag 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/8972207583262167360


For feedback, file a bug with component Speed>Bisection

Ref moved at the same time, we can close this.