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

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


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

android-nexus7v2
chromium-rel-mac11-pro
chromium-rel-mac12
chromium-rel-win10
chromium-rel-win7-gpu-intel
chromium-rel-win7-gpu-nvidia
chromium-rel-win7-x64-dual

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

=== BISECT JOB RESULTS ===
Bisect failed unexpectedly

Bisect was aborted with the following:
  Step('Bisecting revision.Post bisect results (4)') failed with return_code 1


Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : rasterize_and_record_micro.top_25
  Metric       : rasterize_time/file___static_top_25_yahoogames.html

Revision             Result                   N
chromium@514321      36.1692 +- 0.41292       6      good
chromium@514342      36.1883 +- 0.615597      6      good
chromium@514352      36.0042 +- 0.636313      6      good
chromium@514362      152.817 +- 1.85948       6      bad
chromium@514402      153.201 +- 2.11056       6      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=file...static.top.25.yahoogames.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/8963478156092230576


For feedback, file a bug with component Speed>Bisection

The ref build jumps along with the ToT here, looks like a change to the benchmark. Has gone back to normal now.