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

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


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

android-nexus5X

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/11f2711a240000

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

Update docs preview URL in presubmit by rmistry@google.com
https://skia.googlesource.com/skia/+/5c646cf10fd9f4db788d3993ea73093649306e80

Make components behave the same on android and elsewhere. by thakis@chromium.org
https://chromium.googlesource.com/chromium/src/+/0ffeb3f08464644582f40e9e7c41ffdfab00a836

Fix regression in thread_times.key_mobile_sites_smooth by yiyix@chromium.org
https://chromium.googlesource.com/chromium/src/+/be2578711ee47f8b8a5ba8b15108dedb50a27367

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

the improvement was due to this cl, https://chromium-review.googlesource.com/c/chromium/src/+/1029733 and it has cause more 20 regression in other metrics. the cl mentioned here, has fixed those regressions and  smoothness.top_25_smooth timing is back to the point before the fake improvement. No bug.