[FFmpeg-trac] #7690(undetermined:new): FFmpeg QSV decode + VPP performance is just a fraction of what one gets with VA-API and MediaSDK

[FFmpeg]

#7690: FFmpeg QSV decode + VPP performance is just a fraction of what one gets
with VA-API and MediaSDK
-------------------------------------+-------------------------------------
             Reporter:  eero-t       |                    Owner:
                 Type:  defect       |                   Status:  new
             Priority:  normal       |                Component:
              Version:  git-master   |  undetermined
             Keywords:  qsv          |               Resolution:
             Blocking:               |               Blocked By:
Analyzed by developer:  0            |  Reproduced by developer:  0
-------------------------------------+-------------------------------------

Comment (by eero-t):

 > There is really no reason to use it, specially as it's lacking a lot of
 features VAAPI (and Windows QSV) has, and apparently also performs notably
 worse.

 In FFmpeg transcode operations, their performance seems on par, depending
 on case and HW, sometimes VA-API is marginally faster, sometimes QSV.  In
 most cases both are a bit faster than the old i965 driver, but not always
 (because old i965 and new iHD driver seem to split work differently
 between compute and video engines).

 From the feature support side, VA-API has issue #7650, which isn't a
 problem with QSV.


 > I suppose this an issue of qsv hwdownloading

 I'll do some additional comparisons for doing just decoding, and doing
 decoding + downscaling, to see how it impacts the perf gap, and report the
 results tomorrow.

--
Ticket URL: <https://trac.ffmpeg.org/ticket/7690#comment:9>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker