decoded_frame_count perf test misleading |
|||
Issue descriptionThe linux-release/media.tough_video_cases/decoded_frame_count tests note that "lower is better". If this number represents the number of frames actually decoded, then it should be "higher is better". Example: https://chromeperf.appspot.com/report?sid=9255d86c9c9a1a55029f5e741cf674c48ae3cda707d50781cbb9854abb519c5e&rev=467944 When it dropped from 550 to 300 that should be a problem, not an improvement.
,
May 8 2017
I'm going to look into the original design documents to try to understand what was intended here: https://docs.google.com/document/d/1r7UY9n7ng7Z0VtDIWjhC9LbuIhMSiIdHgb-yTthsfKs/edit# https://docs.google.com/document/d/1hPYo9BFwqFgHXrM0OslXOjjMLwDA0QWIiLwaWsfTHOY/edit#
,
Jun 7 2017
Work is progressing here: https://docs.google.com/document/d/1TvUWPl6diK3DTJdSWMOcdz-6qnKC6KEHAZqoBBD8lIc/edit#heading=h.pbl9canvrafx I think the right solution is to simply stop alerting on these.
,
Jul 10 2017
I fixed this to no longer alert on decoded_frame_count. |
|||
►
Sign in to add a comment |
|||
Comment 1 by jrumm...@chromium.org
, May 8 2017