New issue
Advanced search Search tips

Issue 919511 link

Starred by 1 user
Status: WontFix
Owner:
boliu@chromium.org
Closed: Jan 7
Cc:
boliu@chromium.org
mustaq@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

1.4%-56.8% regression in rendering.mobile/tasks_per_frame_total_all at 619930:620011

Project Member Reported by mustaq@chromium.org, Jan 7 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Jan 7 

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

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


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
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Jan 7

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

aw: Post resource returns by boliu@chromium.org
https://chromium.googlesource.com/chromium/src/+/860d715842a49229bd509f7fc9d281114ccdecb4
tasks_per_frame_total_all: 50.61 → 55.03 (+4.422)

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

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

Comment 4 by boliu@chromium.org, Jan 7

Status: WontFix (was: Assigned)
This is expected, since all resource returns are posted to UI thread now.

More interested if there is any memory regression..
►

Sign in to add a comment