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

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


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

android-nexus5x-perf

blink_perf.dom - Benchmark documentation link:
  https://bit.ly/blink-perf-benchmarks

blink_perf.layout - Benchmark documentation link:
  https://bit.ly/blink-perf-benchmarks

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/16838920e40000

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

Remove support for ETC1 tiles by piman@chromium.org
https://chromium.googlesource.com/chromium/src/+/09c2f5373c61735db0dfedffb96608212f0d9e44
21.72 → 22.56 (+0.84)

Remove the runtime flag for test reports. by paulmeyer@chromium.org
https://chromium.googlesource.com/chromium/src/+/96a4668d39b28f933b44801b594aa91cdd32f87b
23.25 → 24.48 (+1.228)

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

Benchmark documentation link:
  https://bit.ly/blink-perf-benchmarks

I don't believe my CL could have had any impact on... anything at all really, let alone performance. I'll punt to piman@ in case he has any ideas.

My CL only removes dead code.
Sounds like a case of a bad benchmark.