Issue metadata
Sign in to add a comment
|
11.2% regression in video_WebRtcCamera at 33830001055300000:33900001055400000 |
||||||||||||||||||
Issue descriptionI haven't looked too deeply into where and how total_num_frames is calculated, but I browsed through the CLs and picked out a few candidates. https://webrtc.googlesource.com/src.git/+log/8058fbbd6bc0..448f4d50dc75 (Some CLs related to rate allocation and frame dropping.) https://chromium-review.googlesource.com/c/chromium/src/+/963642 (Enable GPU memory buffer for video. Not sure if this affects capture, renderer or both.) Also not sure how much time we should spend on this. https://bugs.chromium.org/p/chromium/issues/detail?id=813522 suggests that total_num_frames isn't a very interestingmetric on it's own.
,
May 22 2018
I don't think any of my commits (which are all about VP9 SVC) could cause this regression.
,
Jan 10
Downgrading P2s that haven't been modified in more than 6 months, which have no component or owner.
,
Jan 11
Available, but no owner or component? Please find a component, as no one will ever find this without one. |
|||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, May 8 2018