New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 762843 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Closed: Sep 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Feature



Sign in to add a comment

Add 4K@60fps vp9 streams in video_PlaybackPerf and video_VDAPerf

Project Member Reported by hiroh@chromium.org, Sep 7 2017

Issue description

It would be useful autotest reports 4K/60fps vp9 video playback performance.
After a 4K/60fps can be used for video_PlaybackPerf and video_VDAPerf, the results will be shown in chromeperf.appspot.com.
 

Comment 1 by hiroh@chromium.org, Sep 7 2017

Currntly, a VP9/30fps is used fro video_PlaybackPerf and no vp9 video is used for video_VDAPerf.
I am going to use VP9/60fps video in crosvideo.appspot.com as a new test video.

Comment 2 Deleted

Comment 3 Deleted

Comment 4 Deleted

Comment 5 by hiroh@chromium.org, Sep 8 2017

Because VDA unittest counts the number of superframes as its decoded_frames.
I had to check the generated video superframs.
I used following commands to generate 600 superframes video, where the number of video frames, not superframes, must be passed to ffmpeg.

$ ffmpeg -i 2160_60_vp9.webm -an -sn -vcodec copy -vframes 645 2160_60_10s_600frames.vp9.webm

The number of superframes could be checked by the following command.
$ ffmpeg -i 2160_60_10s_600frames.vp9.webm -an -sn -vcodec copy -bsf vp9_superframe -f null /dev/null  2>&1| grep frame=

The vp9 raw stream used in VDA unittest, which is ivf format precisely, were generated by the following command.

$ ffmpeg -i 2160_60_10s_600frames.vp9.webm -an -sn -vcodec copy 2160_60_10s_600frames.vp9.ivf && mv 2160_60_10s_600frames.vp9.ivf 2160_60_10s_600frames.vp9

Comment 6 by hiroh@chromium.org, Sep 9 2017

The video in crosvideo.appspot.com was downloaded from https://www.youtube.com/watch?time_continue=2&v=qrX0jzOecPc.
It's a creative common license and reusing it is no problem.
I uploaded the video to gcloud.
gs://chromiumos-test-assets-public/Shaka-Dash/2160_60_10s_600frames-2fd17338cb4d9cfd9d7299a108ca9145.vp9.webm
gs://chromiumos-test-assets-public/Shaka-Dash/2160_60_10s_600frames-9997299a4e2c853ab2543fc2f813294a.vp9

Comment 7 by hiroh@chromium.org, Sep 9 2017

video_VDAPerf was failed on kevin in all the format cases, not only vp9 60fps case, although video_VDAPlaybackPerf and VDA unittest were passed.
Codereview is crrev.com/c/657499.

Comment 8 by hiroh@chromium.org, Sep 14 2017

Cc: kcwu@chromium.org
Verified on elm.
Code review is crosreview.com/657499.
The performance data would not be shown immediately due to crbug.com/765067.

Project Member

Comment 9 by bugdroid1@chromium.org, Sep 15 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/autotest/+/7387d434fb7c3f98a07cce9166aa224d52ccac9e

commit 7387d434fb7c3f98a07cce9166aa224d52ccac9e
Author: Hirokazu Honda <hiroh@chromium.org>
Date: Fri Sep 15 03:14:17 2017

autotest: Add 4K/60fps streams to video_PlaybackPerf and video_VDAPerf

Autotest reports 4K/60fps vp9 video playback performance
through video_PlaybackPerf and video_VDAPerf.
The results would be shown in chromeperf.appspot.com

BUG= chromium:762843 
TEST=video_VDAPerf and video_PlaybackPerf on kevin

Change-Id: I2278b464e5eb9b56be7fedb6edadf9bb9131cb15
Reviewed-on: https://chromium-review.googlesource.com/657499
Commit-Ready: Hirokazu Honda <hiroh@chromium.org>
Tested-by: Hirokazu Honda <hiroh@chromium.org>
Reviewed-by: Kuang-che Wu <kcwu@chromium.org>

[add] https://crrev.com/7387d434fb7c3f98a07cce9166aa224d52ccac9e/client/site_tests/video_VDAPerf/control.vp9.4k
[add] https://crrev.com/7387d434fb7c3f98a07cce9166aa224d52ccac9e/client/site_tests/video_PlaybackPerf/control.vp9.4k.60

Comment 10 by hiroh@chromium.org, Sep 15 2017

Blockedon: 765067
The patch was merged.
I am going to close this issue after the performance data are shown chromeperf.spot.com.

Comment 11 by hiroh@chromium.org, Sep 25 2017

Blockedon: -765067
Status: Verified (was: Started)
I confirmed that the additional elements were shown on chromeperf.appspot.com.

Sign in to add a comment