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

Issue 886662 link

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



Sign in to add a comment

2.5%-700.1% regression in rendering.mobile at 591671:591738

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

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

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

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


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

Android Nexus5 Perf

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

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

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

[config] Enable scheduled script streaming field trial by leszeks@chromium.org
https://chromium.googlesource.com/chromium/src/+/7eb2bb6769b38736fc75a12c15563c4a69f1a61f
7.216 → 56.95 (+49.73)

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

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

Comment 4 by leszeks@chromium.org, Sep 24

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

Sign in to add a comment