New issue
Advanced search Search tips

Issue 905163 link

Starred by 1 user
Status: Assigned
Owner:
timvolod...@chromium.org
Cc:
chiniforooshan@chromium.org
timvolod...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

14.1% regression in rendering.mobile/thread_total_all_cpu_time_per_frame at 605022:605072

Project Member Reported by chiniforooshan@chromium.org, Nov 14 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Nov 14 

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

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


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

Android Nexus5X WebView Perf

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

Comment 3 by 42576172...@developer.gserviceaccount.com, Nov 14

Cc: timvolod...@chromium.org
Owner: timvolod...@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/10cfc8cbe40000

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

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

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

Sign in to add a comment