New issue
Advanced search Search tips

Issue 889138 link

Starred by 1 user
Status: WontFix
Owner:
leszeks@chromium.org
Closed: Dec 14
Cc:
leszeks@chromium.org
lanwei@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

6%-28.6% regression in rendering.mobile/thread_total_all_cpu_time_per_frame at 591671:591738

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

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

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

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


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 28

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/158b944f640000

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

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

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

Comment 4 by leszeks@chromium.org, Dec 14 

WAI, more streaming == more cpu use.

Comment 5 by leszeks@chromium.org, Dec 14

Status: WontFix (was: Assigned)
►

Sign in to add a comment