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

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


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

chromium-rel-win7-gpu-intel

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/10137c8f840000

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

Roll clang 321529:324578 by hans@chromium.org
https://chromium.googlesource.com/chromium/src/+/ca5066b992b8a05e6a3df042f2c0e1766e13a565

Merge in  CL/184825316 -- fixes to IETF Framing to work properly in Chromium by fkastenholz@chromium.org
https://chromium.googlesource.com/chromium/src/+/313f3c31a4dff0276dcd70f69afdf881e65e525f

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

The cl by fkastenholz https://chromium.googlesource.com/chromium/src/+/313f3c31a4dff0276dcd70f69afdf881e65e525f changes code that is not actually used in chrome and can't be the source of this regression.

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/16963b3f840000

📍 Found significant differences after each of 3 commits.
https://pinpoint-dot-chromeperf.appspot.com/job/16963b3f840000

Migrate RemoveFormattingAndStyle() into ExecuteRemoveFormat(). by zhuoyu.qian@samsung.com
https://chromium.googlesource.com/chromium/src/+/48a953f5401b8941f9f4bf2922ca6db442c9749d

Refactor manually_expanded_or_collapsed flag in Notification by yoshiki@chromium.org
https://chromium.googlesource.com/chromium/src/+/94f9c98a36c6e80fc66aac364ba24ad9408cf6e8

Roll clang 321529:324578 by hans@chromium.org
https://chromium.googlesource.com/chromium/src/+/ca5066b992b8a05e6a3df042f2c0e1766e13a565

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

Looking at the graph, this movement doesn't seem significant.