New issue
Advanced search Search tips

Issue 860113 link

Starred by 1 user
Status: WontFix
Owner:
dstaessens@chromium.org
Closed: Jul 4
Cc:
mcasas@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Video decode performance regression on Chrome OS

Project Member Reported by dstaessens@chromium.org, Jul 4 
Chrome Version: 69.0.3473.0 - 69.0.3474.0
Chrome OS Version: 69.10820.0.0 - 69.10824.0.0
Chrome OS Platform: verified on Eve

Chrome commit c1ee562516e98cb7066bca4614f94ea7beec06aa introduced some changes to the VAAPI. These changes seem to cause the HW accelerator initialization to fail in some cases. The change was reverted in 9921f96141b3172c6a38dd1f42d4acfb0507ae96 due to other reasons. As this change is to be reintroduced, I created this bug to investigate the issue.

When running the 'video_PlaybackPerf.h264' test, the histograms show a Media.GpuVideoDecoderInitializeStatus error of 15 (DECODER_ERROR_NOT_SUPPORTED). This causes a large performance regression. This doesn't seem to happen when playing the testfile used in the test manually, or when playing h264 videos from crosvideo.appspot.com manually.

I added log files for the case where the regression is present, and the case where commit c1ee562516e98cb7066bca4614f94ea7beec06aa was reverted.
log_regression.txt
2.1 MB View Download
log_reverted.txt
2.1 MB View Download
results-chart_regression.json
1.1 KB View Download
results-chart_reverted.json
1.1 KB View Download

Comment 1 by dstaessens@chromium.org, Jul 4

Description: Show this description

Comment 2 by dstaessens@chromium.org, Jul 4

Summary: Video decode performance regression on Chrome OS (was: HW decoder initialization failure)

Comment 3 by dstaessens@chromium.org, Jul 4 

I'm not certain the performance regression is related to the 'DECODER_ERROR_NOT_SUPPORTED' error, as I've also seen this occur with the change reverted. I think that error might be caused by the v4l2 initialization failing, which shows up in the test logs but doesn't seem to affect the test otherwise.
►

Sign in to add a comment