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

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


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

mac-10_12_laptop_low_end-perf

rendering.desktop - Benchmark documentation link:
  https://bit.ly/rendering-benchmarks

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/17b2013f640000

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

Reland "Scheduler: WebURLLoader should notify Blink with the initial priority." by yhirano@chromium.org
https://chromium.googlesource.com/chromium/src/+/9fbd6bbc97324bc72d8fcb7bb7a846399517fdee
2.737 → 7.156 (+4.418)

bindings: Update V8Document::InstallRuntimeOnTemplate by peria@chromium.org
https://chromium.googlesource.com/chromium/src/+/d14e46fd2d04affa773b2048a2a93ae8d6116a11
6.23 → 9.758 (+3.528)

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

Benchmark documentation link:
  https://bit.ly/rendering-benchmarks

Mine was a reland change as part of sheriff duty.

Issue 880383 has been merged into this issue.

Ok, now I'm convinced that it is http://crrev.com/c/1185593. However, given that it's only small EQT regression and there are known improvements in loading time ( issue 883382 ), I'm tempted to close this as won't fix.