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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg8vO4sQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgiri0kQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgiur3-AkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgyr3ypAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgitGWqwsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgiuPj8QkM


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

chromium-rel-win7-gpu-intel
chromium-rel-win7-gpu-nvidia
chromium-rel-win7-x64-dual
chromium-rel-win8-dual

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

Assigning to OWNER to take a look...

NOTE: The Chrome Perf Dashboard cannot handle the "normal workload" here, and there are about 120 data series that I was not able to add to this bug group without JavaScript timing out. I've batch-marked them all as invalid since they all look the same (same random behavior and rev-range).

Perf sheriff ping: reminder to follow up on possible performance issues

I believe this is caused by Flash now running on these pages which is as intended.  Merging into related issue.