New issue
Advanced search Search tips

Issue 898892 link

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



Sign in to add a comment

2.9%-196.4% regression in rendering.mobile/avg_surface_fps at 601341:601406

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

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

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

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


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, Oct 25

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/1393a19ae40000

viz: Throttle begin-frames when gpu is busy. by sadrul@chromium.org
https://chromium.googlesource.com/chromium/src/+/5c2e137dc5294b30492a05a96a33bf0c7ff12908
queueing_durations: 0.1809 → 0.408 (+0.2271)

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

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

Sign in to add a comment