Media (Intel® Video Processing Library, Intel Media SDK)
Access community support with transcoding, decoding, and encoding in applications using media tools like Intel® oneAPI Video Processing Library and Intel® Media SDK
Announcements
The Intel Media SDK project is no longer active. For continued support and access to new features, Intel Media SDK users are encouraged to read the transition guide on upgrading from Intel® Media SDK to Intel® Video Processing Library (VPL), and to move to VPL as soon as possible.
For more information, see the VPL website.
3043 Discussions

HEVC decode performance

john_h_1
Beginner
‎03-16-2017 03:06 PM
369 Views

We are bench marking HEVC decode performance on an i7-7700K Kaby Lake (4.2GHz), with 32GB of DDR4.  We just installed the latest 2017 Media SDK (LInux). We use ffmpeg with the hevc_qsv codec.

The video input streams are HEVC 4K (3840x2160), 10-bit, 100Mbps, 60fps. Our output format is v210 (422, 10-bit). Our output destination is just "-f null -" so the only I/O should just be reading the encoded file from an SSD.  E.g.,

        ffmpeg -y -benchmark -hwaccel qsv -i Videos/uhd100b.ts -vcodec v210  -f null -

We were hoping/expecting to see decode rates at or better than real-time. However, ffmpeg reports "speed" at about 0.70x. The CPU load is evenly distributed over 8 cores, at about 55% per core. What performance should we expect?

Thanks in advance for any insight.

0 Kudos

Link Copied

0 Replies
Reply

Community support is provided during standard business hours (Monday to Friday 7AM - 5PM PST). Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.