New issue
Advanced search Search tips

Issue 845114 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: May 2018
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

164.2% regression in webrtc_perf_tests at 23310:23311

Project Member Reported by nisse@chromium.org, May 21 2018

Issue description

See the link to graphs below.
 
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, May 21 2018

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

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


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

webrtc-android-tests-nexus6-nougat

Comment 2 by nisse@chromium.org, May 21 2018

Owner: ssilkin@chromium.org
Large perf change after vp9 screensharing changes of cl https://webrtc-review.googlesource.com/76801. An expected improvement? Sergey, can you have a look and confirm?
Status: WontFix (was: Untriaged)
It is not expected outcome but since this the change is positive (time between freezes increased) no actions are needed.

PS. Why do we run these perf tests on such weak device? It takes 140ms to encode frame.

Comment 4 by nisse@chromium.org, May 21 2018

Note that the alerts are for a range of android devices, from nexus4 and nexus7 (pretty old, I think) to a newer pixel device.

Sign in to add a comment