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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg6sSJ8woM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg6u7hpwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg6qLMrQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg6sSdqgsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgqtP58wkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg6rDHuQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgqtP58woM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgqueLrAsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg6uqwoQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg6rjshAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgqtO3-woM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgqtO3-wgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgqs76_QsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg6vXZpQoM


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

android-nexus5X
android-nexus6
android-nexus7v2
chromium-rel-mac-retina
chromium-rel-win7-gpu-intel
chromium-rel-win7-x64-dual
chromium-rel-win8-dual

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

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

Bisect Details
  Configuration: mac_retina_perf_bisect
  Benchmark    : speedometer
  Metric       : jQuery-TodoMVC/jQuery-TodoMVC

Revision             Result                  N
chromium@471248      575.169 +- 46.5068      21      good
chromium@471297      569.255 +- 52.553       21      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests speedometer

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8979526616441739552

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5810570042802176


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!

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

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

Bisect Details
  Configuration: mac_retina_perf_bisect
  Benchmark    : speedometer
  Metric       : jQuery-TodoMVC/jQuery-TodoMVC

Revision             Result                  N
chromium@471248      569.044 +- 30.4993      21      good
chromium@471297      567.218 +- 36.1799      21      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests speedometer

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8979518408386209680

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5810570042802176


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!

Hi Michael, the ref score on this machine went up as well. That could indicate e.g. a hardware change.

graphs recovered