New issue
Advanced search Search tips

Issue 755949 link

Starred by 1 user
Status: WontFix
Owner:
eladalon@chromium.org
Closed: Aug 2017
Cc:
nisse@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

7%-100% improvement in webrtc_perf_tests at 19214:19218

Project Member Reported by nisse@chromium.org, Aug 16 2017 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Aug 16 2017 

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

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


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

webrtc-win-large-tests

Comment 2 by nisse@chromium.org, Aug 16 2017

Owner: eladalon@chromium.org
Hi, this changes in encode time and cpu usage, on windows, appeared close to your demuxer and flexfec changes. Commit range is 19214-19218, including your changes and one chromium roll. Can you have a look to see if changes are reasonable and/or expected?

Comment 3 by eladalon@chromium.org, Aug 18 2017

Status: WontFix (was: Untriaged)
Looking at the CLs in question, I doubt I could take credit for this.
►

Sign in to add a comment