New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 855435 link

Starred by 1 user
Status: Duplicate
Owner:
chaopeng@chromium.org
Closed: Jun 2018
Cc:
chaopeng@chromium.org
█ alexclarke@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

13.6%-89.6% regression in thread_times.key_mobile_sites_smooth at 568534:568711

Project Member Reported by alexclarke@chromium.org, Jun 22 2018 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Jun 22 2018 

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

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


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

android-nexus5
android-one
android-webview-nexus5X
android-webview-nexus6
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Jun 25 2018

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

Set TouchStartExpectedSoon only after we seen a blocking event by chaopeng@chromium.org
https://chromium.googlesource.com/chromium/src/+/4a2ebc8dad89ca0042d0babd619f4ea35e3ac072
1.346 → 2.351 (+1.006)

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

Comment 4 by chaopeng@chromium.org, Jun 25 2018

Mergedinto: 855443
Status: Duplicate (was: Assigned)
►

Sign in to add a comment