New issue
Advanced search Search tips

Issue 894446 link

Starred by 1 user
Status: WontFix
Owner:
ssilkin@chromium.org
Closed: Oct 19
Cc:
ilnik@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

1.1%-35.4% regression in webrtc_perf_tests at 24978:24991

Project Member Reported by ilnik@chromium.org, Oct 11 
This CL:
https://webrtc.googlesource.com/src/+/e7ce888abe3ff228cda24da7bf9326003f037c92

Changed some vp9ksvc tests. PTAL if this is expected.
Project Member

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

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

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


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

webrtc-android-tests-nexus4-lollipop
webrtc-android-tests-nexus5-kitkat
webrtc-android-tests-nexus6-nougat

Comment 2 by ssilkin@chromium.org, Oct 19

Status: WontFix (was: Assigned)
All changes are expected.

1) send_bandwidth/media_bitrate: decreased. Before the fix, it actually exceeded the link capacity (1mbps).
2) encode_time/cpu_usage: decreased. This is the consequence of (1) - video allocation decreased, sender doesn't produce HD spatial layer.
3) ssim/psnr: slightly decreased. This is the consequence of (1) - video allocation decreased.
►

Sign in to add a comment