New issue
Advanced search Search tips

Issue 879685 link

Starred by 1 user
Status: Assigned
Owner:
sunn...@chromium.org
Cc:
sunn...@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

34.6% regression in rendering.mobile at 587671:587775

Project Member Reported by sunn...@chromium.org, Aug 31 
Might be GPU scheduler?
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Aug 31 

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

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


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

android-nexus5x-perf

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

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

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

Use GPU scheduler for in process command buffer by sunnyps@chromium.org
https://chromium.googlesource.com/chromium/src/+/1405fd6a6c18ce8896ab031005b570d96cfda9fb
50.9 → 33.6 (-17.3)

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

Sign in to add a comment