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

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


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

chromium-rel-mac11-pro

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/103d2d2d840000

📍 Found significant differences after each of 2 commits.
https://pinpoint-dot-chromeperf.appspot.com/job/103d2d2d840000

mac: Fix lock status with surface sync by ccameron@chromium.org
https://chromium.googlesource.com/chromium/src/+/f5beaf48bb825e6b79cfc739360119555f1ea6e3

Roll src/third_party/skia/ 854f68b58..4a657adf7 (1 commit) by skia-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com
https://chromium.googlesource.com/chromium/src/+/4f8736e26a2c91249af29d55cef4e9f247f37485

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions

Assigning to ccameron@ in case this is surface sync related.

Most of the graphs for this bug are for non-Mac.

The f5beaf48bb825e6b79cfc739360119555f1ea6e3 change may have caused this, but it also had just massively improved

Thanks, ccameron! I moved the non-Mac regressions to  bug 816725 . So now this bug is about a single regression to a single page on 10.11 only. According to #5, there are also improvements, and looking here I do see several in the range on Mac: https://chromeperf.appspot.com/group_report?rev=535323

WontFix-ing this, but feel free to reopen if anyone feels it needs deeper investigation.