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

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


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

Android Nexus5X WebView Perf
Android Nexus6 WebView Perf

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

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/1678f7d1e40000

📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/1678f7d1e40000

[AW SystemWebViewShell] Increase target_sdk version to 28 (P) and enable cleartext traffic by timvolodine@chromium.org
https://chromium.googlesource.com/chromium/src/+/6d8de33fc1d2308a01dea2d59b7b58c137d63deb
queueing_durations: 0.4575 → 1.92 (+1.463)

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

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

The only this the patch referenced here does is:
1. increase targetSdk version of the systemwebviewshell from 24 (N) to 28 (P).
2. allow cleartext traffic (which is backwards compatible)

Not sure how this would impact rendering times, and if it does this might be the result of rendering changes in P..

Also it looks like only the techcrunch_mobile_2018 test is impacted, so there might be something specific about the actual test.

+cc:sadrul@,vmiura@ who are owners of rendering.mobile tests

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