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

Issue 887302 link

Starred by 1 user
Status: Duplicate
Merged: issue 888558
Owner: ----
Closed: Sep 24
Cc:
oysteine@google.com
█ alexclarke@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

1.4%-131.4% regression in rendering.mobile at 592113:592229

Project Member Reported by alexclarke@chromium.org, Sep 20 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Sep 20 

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

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


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

Android Nexus5 Perf
android-nexus5x-perf

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

Comment 3 by 42576172...@developer.gserviceaccount.com, Sep 23

Cc: oysteine@google.com
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/10a4441f640000

Reland "Enable Perfetto by default for all telemetry tests" by oysteine@google.com
https://chromium.googlesource.com/chromium/src/+/0f374eff414ec0683aafbe2aae3fd405a4fcc221
0.2718 → 0.5665 (+0.2947)

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

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

Comment 4 by pasko@chromium.org, Sep 24

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

Sign in to add a comment