{"id":551,"date":"2008-08-18T11:00:07","date_gmt":"2008-08-18T09:00:07","guid":{"rendered":"https:\/\/alax.info\/blog\/?p=551"},"modified":"2016-09-09T18:45:18","modified_gmt":"2016-09-09T16:45:18","slug":"an-effect-of-excessive-rgb-conversion-onto-video-streaming-perofrmance-continued","status":"publish","type":"post","link":"https:\/\/alax.info\/blog\/551","title":{"rendered":"An effect of excessive RGB conversion on video streaming performance (continued)"},"content":{"rendered":"

This continues the topic raised by previous post<\/a>. As fairly noticed by The March Hare<\/a>, video renderer is using hardware overlay and the benchmark is incorrect if we are to extrapolate the performance to scenario with multiple video renderers.<\/p>\n

So, an updated test application creates 16 video renderers with 16 threads pumping two meida samples through each of the 16 filter graphs.<\/p>\n

\"\"<\/a><\/p>\n

The screen shot shows that there is only one video overlay in use (which image was not captured and blackness is shown instead), so results may be inaccurate for one of the graph among 16. In this simple test I disregard this.<\/p>\n

Here go the results (in all tests CPU usage is maxed out):<\/p>\n