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

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


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

chromium-rel-win7-gpu-ati
chromium-rel-win7-gpu-nvidia

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

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

Bisect Details
  Configuration: winx64ati_perf_bisect
  Benchmark    : rasterize_and_record_micro.top_25
  Metric       : record_time/file___static_top_25_booking.html

Revision             Result                       N
chromium@502527      0.0859524 +- 0.00222539      21      good
chromium@502529      0.0859524 +- 0.00299205      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=file...static.top.25.booking.html rasterize_and_record_micro.top_25

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

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


For feedback, file a bug with component Speed>Bisection

Looks like a glitch.