New issue
Advanced search Search tips

Issue 911132 link

Starred by 2 users

Issue metadata

Status: Duplicate
Merged: issue 906540
Owner: ----
Closed: Dec 5
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

A zero-to-nonzero to 87% regression in rendering.mobile/queueing_durations at 611029:612530

Project Member Reported by maxlg@chromium.org, Dec 3

Issue description

See the link to graphs below.
 
All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=911132

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


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
Likely a dupe of  Issue 911129 
😿 Pinpoint job stopped with an error.
https://pinpoint-dot-chromeperf.appspot.com/job/1112b637e40000

The swarming task expired. The bots are likely overloaded, dead, or misconfigured.
Mergedinto: 906540
Status: Duplicate (was: Untriaged)
Cc: eroman@chromium.org
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/10949514140000

Recognize --proxy-bypass-list from WebView. by eroman@chromium.org
https://chromium.googlesource.com/chromium/src/+/4bc3f6d6ec942c97293e303f469ccdc4bf551fc2
thread_raster_cpu_time_per_frame: No values → 0.1054

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

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

Sign in to add a comment