New issue
Advanced search Search tips

Issue 899326 link

Starred by 1 user
Status: WontFix
Owner:
sadrul@chromium.org
Closed: Oct 26
Cc:
sande...@chromium.org
sadrul@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

32%-99.6% regression in media.mobile at 602454:602552

Project Member Reported by sandersd@google.com, Oct 26 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Oct 26 

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

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


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

Android Nexus5 Perf
android-nexus5x-perf

media.mobile - Benchmark documentation link:
  None
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Oct 26

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

Revert "viz: Throttle begin-frames when gpu is busy." by sadrul@chromium.org
https://chromium.googlesource.com/chromium/src/+/3629d825012de4e1ce8cad1a2be9b654c7b01b6a
memory:chrome:all_processes:reported_by_chrome:gpu:effective_size: 9.539e+06 → 1.77e+07 (+8.166e+06)

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

Benchmark documentation link:
  None

Comment 4 by sande...@chromium.org, Oct 26

Status: WontFix (was: Assigned)
►

Sign in to add a comment