Inline image 1Writing in this email list because i was told by Gstreamer-VAAPI devs that this is a driver issue, it has nothing to do with Gstreamer When transcoding live stream with Gstreamer-VAAPI a lot more of GPU resources are being used then when using Gstreamer-MSDK. Live Transcode VAAPI: GPU 27% Live Transcode MSDK: GPU 6% VAAPI seems to be using 4 times more GPU then MSDK. Please see the attached image I took screenshot of both servers. Environment: 2x identical servers with Xeon(R) CPU E3-1245 v5 SKYLAKE Server 1 with VAAPI: Ubuntu 16.04 vainfo: Driver version: Intel i965 driver for Intel(R) Skylake - 1.8.2.pre1 (1.7.3-372-g2f0a844) Gstreamer-VAAPI Pipeline: gst-launch-1.0 souphttpsrc location="http://localhost:80/oranews_HD/mpegts" is-live=true ! tsdemux name=demux ! queue max-size-buffers=1200 max-size-buffers=0 max-size-time=0 ! \ h264parse ! vaapih264dec ! vaapipostproc width=1280 height=720 ! vaapih264enc rate-control=2 bitrate=1700 ! h264parse ! \ flvmux streamable=true name=mux ! rtmpsink location="rtmp://localhost:1935/pushrtmp/vappi_outs live=1" demux. ! queue max-size-buffers=1200 max-size-buffers=0 max-size-time=0 ! \ mpegaudioparse ! queue ! avdec_mp2float plc=true ! audioconvert ! queue ! voaacenc bitrate=128000 ! mux. Server 2 with MSDK: Centos 7.2 Media Server Studio 2017 vainfo: VA-API version: 0.99 (libva 1.67.0.pre1) Gstreamer-MSDK Pipeline: gst-launch-1.0 souphttpsrc location="http://localhost:80/oranews_HD/mpegts" is-live=true ! tsdemux name=demux ! queue max-size-buffers=1200 max-size-buffers=0 max-size-time=0 \ ! h264parse ! mfxh264dec ! mfxvpp width=1280 height=720 ! mfxh264enc rate-control=1 bitrate=1700 ! flvmux streamable=true name=mux ! rtmpsink location="rtmp://localhost:1935/pushrtmp/mfx_out live=1" demux. \ ! queue max-size-buffers=1200 max-size-buffers=0 max-size-time=0 ! mpegaudioparse ! queue ! avdec_mp2float plc=true ! audioconvert ! queue ! voaacenc bitrate=128000 ! mux. -- Benjamin DRESHAJ - CTO SetPlex LLC. Address. 2320 Arthur Ave - Bronx, NY 10458 - USA Tel. ++1 718.213.4282 - Fax. ++1 718.701.4407 Mobile. ++1 646.283.3439 - Mail. ben(a)ftamarket.com <mailto:ben@ftamarket.com> Web. www.setplex.com <http://www.setplex.com> - www.tvalb.com <http://www.tvalb.com> - www.italotv.com <http://www.italotv.com> ------------------------------------------------------------------------------------------------------------------------------------------------ This message contains confidential information and is intended only for the intended recipient(s). If you are not the named recipient you should not read, distribute or copy this e-mail. Please notify the sender immediately via e-mail if you have received this e-mail by mistake; then, delete this e-mail from your system. ------------------------------------------------------------------------------------------------------------------------------------------------ _______________________________________________ intel-vaapi-media mailing list intel-vaapi-media(a)lists.01.org https://lists.01.org/mailman/listinfo/intel-vaapi-media

Hi Benjamin, If I correctly understood the parameters of intel-gpu-top, the "render-busy" is including the shared VME block. If you set the "tune=low-power" , the the value you see in "render-busy" should go down significantly (because there is fixed function for doing vme) The MSDK driver you use might be using the low-power mode by default, I dont know :) Also would be good to test with and without scaling or whatever postprocessing . On 04/10/2017 03:03 PM, Benjamin Dreshaj wrote: [image: Inline image 1]Writing in this email list because i was told by Gstreamer-VAAPI devs that this is a driver issue, it has nothing to do with Gstreamer When transcoding live stream with Gstreamer-VAAPI a lot more of GPU resources are being used then when using Gstreamer-MSDK. Live Transcode VAAPI: GPU 27% Live Transcode MSDK: GPU 6% VAAPI seems to be using 4 times more GPU then MSDK. Please see the attached image I took screenshot of both servers. Environment: 2x identical servers with Xeon(R) CPU E3-1245 v5 SKYLAKE Server 1 with VAAPI: Ubuntu 16.04 vainfo: Driver version: Intel i965 driver for Intel(R) Skylake - 1.8.2.pre1 (1.7.3-372-g2f0a844) Gstreamer-VAAPI Pipeline: gst-launch-1.0 souphttpsrc location="http://localhost:80/oranews_HD/mpegts" is-live=true ! tsdemux name=demux ! queue max-size-buffers=1200 max-size-buffers=0 max-size-time=0 ! \ h264parse ! vaapih264dec ! vaapipostproc width=1280 height=720 ! vaapih264enc rate-control=2 bitrate=1700 ! h264parse ! \ flvmux streamable=true name=mux ! rtmpsink location="rtmp://localhost:1935/pushrtmp/vappi_outs live=1" demux. ! queue max-size-buffers=1200 max-size-buffers=0 max-size-time=0 ! \ mpegaudioparse ! queue ! avdec_mp2float plc=true ! audioconvert ! queue ! voaacenc bitrate=128000 ! mux. Server 2 with MSDK: Centos 7.2 Media Server Studio 2017 vainfo: VA-API version: 0.99 (libva 1.67.0.pre1) Gstreamer-MSDK Pipeline: gst-launch-1.0 souphttpsrc location="http://localhost:80/oranews_HD/mpegts" is-live=true ! tsdemux name=demux ! queue max-size-buffers=1200 max-size-buffers=0 max-size-time=0 \ ! h264parse ! mfxh264dec ! mfxvpp width=1280 height=720 ! mfxh264enc rate-control=1 bitrate=1700 ! flvmux streamable=true name=mux ! rtmpsink location="rtmp://localhost:1935/pushrtmp/mfx_out live=1" demux. \ ! queue max-size-buffers=1200 max-size-buffers=0 max-size-time=0 ! mpegaudioparse ! queue ! avdec_mp2float plc=true ! audioconvert ! queue ! voaacenc bitrate=128000 ! mux. -- Benjamin DRESHAJ - CTO SetPlex LLC. Address. 2320 Arthur Ave - Bronx, NY 10458 - USA Tel. ++1 718.213.4282 <(718)%20213-4282> - Fax. ++1 718.701.4407 <(718)%20701-4407> Mobile. ++1 646.283.3439 <(646)%20283-3439> - Mail. ben(a)ftamarket.com Web. www.setplex.com - www.tvalb.com - www.italotv.com ------------------------------------------------------------ ------------------------------------------------------------ ------------------------ This message contains confidential information and is intended only for the intended recipient(s). If you are not the named recipient you should not read, distribute or copy this e-mail. Please notify the sender immediately via e-mail if you have received this e-mail by mistake; then, delete this e-mail from your system. ------------------------------------------------------------ ------------------------------------------------------------ ------------------------ _______________________________________________ intel-vaapi-media mailing listintel-vaapi-media@lists.01.orghttps://lists.01.org/mailman/listinfo/intel-vaapi-media -- Thanks Sree _______________________________________________ intel-vaapi-media mailing list intel-vaapi-media(a)lists.01.org https://lists.01.org/mailman/listinfo/intel-vaapi-media