Le mercredi 29 mai 2019 à 16:55 -0400, Sven Van Asbroeck a écrit : > Philipp and Fabio, > > On Wed, May 29, 2019 at 12:53 PM Fabio Estevam <festevam@xxxxxxxxx> wrote: > > Does this patch from Philipp fix the problem? > > https://git.pengutronix.de/cgit/pza/linux/commit/?h=imx-drm/fixes&id=137caa702f2308f7ef03876e164b0d0f3300712a > > I am now running 5.2-rc2 with Philipp's non-plus imx6q patch. > > Performance is still much worse than the Freescale baseline. > > I am not at all worried about vpu scaler performance, after all v8 is an > in-progress patch. > > I am much more concerned about the CODA h264 slowdown. My 1080p30 test > video runs at half the speed compared to the Freescale kernel. The best it > can do is 28fps, which results in visible 'jerks' in the video. Note that > this is without using the scaler. > > Questions: > - is the performance slowdown a known issue? > - is there anything I've missed in the gstreamer pipelines below? > - is there anything I can do to help? > > A) mainline 5.2-rc2 with Philipp's latest non-plus patch: > $ time gst-launch-1.0 filesrc > location=/home/default/jellyfish-10-mbps-hd-h264.mkv ! matroskademux ! > h264parse ! v4l2h264dec ! kmssink can-scale=0 sync=0 > real 0m 32.01s kmssink element still have some issues as it renders using the legacy KMS API and makes an synchronous vblank wait before returning. In many cases, the proper workaround is to do: ... ! v4l2h264dec ! queue ! kmssink can-scale=0 sync=0 In order to measure the decoding performance without having the display being involved you can also do: ... ! v4l2h264dec ! fpsdisplaysink text-overlay=0 video-sink=fakevideosink sync=0 -v In order to benefit from the best of this driver, you should also use the latest GStreamer 1.16.0. It contains latest fixes from Philipp and I, including some performance improvement. > > B) Freescale kernel: > $ time gst-launch-0.10 filesrc > location=/home/default/jellyfish-10-mbps-hd-h264.mkv ! decodebin ! > mfw_v4lsink sync=0 > Running time 0:00:14.781129554 render fps 59.941
