Jump to content

GStreamer Based Image Signal Processor/Performance/imx8: Difference between revisions

no edit summary
(Created page with "The following section describes some relevant performance measurements for the RGBA to NV12 color space conversion for a few standard resolutions. It begins with a summary of...")
 
No edit summary
Line 76: Line 76:
</html>
</html>


=CPU usage=
==CPU usage==
These measurements were taken with '''top''' app to monitor the behavior of the pipeline while running. Notice, however, that videotestsrc was used to generate the buffers and it consumes a lot of CPU, so it is likely the results will differ if a camera is used for capture.  
These measurements were taken with '''top''' app to monitor the behavior of the pipeline while running. Notice, however, that videotestsrc was used to generate the buffers and it consumes a lot of CPU, so it is likely the results will differ if a camera is used for capture.  
[[File:Cpu.png|frame|center|CPU usage for CSC kernel.]]
[[File:Cpu.png|frame|center|CPU usage for CSC kernel.]]


=Memory usage=
==Memory usage==
These measurements were taken with '''meminfo''' file to see the behavior of the pipeline while running, but it is important to consider that videotestsrc was used to generate the buffers.
These measurements were taken with '''meminfo''' file to see the behavior of the pipeline while running, but it is important to consider that videotestsrc was used to generate the buffers.
[[File:Memo.png|frame|center|Memory consumption by CSC kernel.]]
[[File:Memo.png|frame|center|Memory consumption by CSC kernel.]]


=Maximum Framerate=
==Maximum Framerate==
These measurements were taken with the '''gst-perf''' tool to monitor the behavior of the pipeline while running. When using videotestsrc we are able to process as many buffers as the element can handle, hence the maximum value reported. The image below shows the maximum framerate that the CSC element supports, which depends on the execution time of the CSC kernel algorithm.
These measurements were taken with the '''gst-perf''' tool to monitor the behavior of the pipeline while running. When using videotestsrc we are able to process as many buffers as the element can handle, hence the maximum value reported. The image below shows the maximum framerate that the CSC element supports, which depends on the execution time of the CSC kernel algorithm.
[[File:Framerate.png|frame|center|Framerate for different resolutions on the CSC kernel.]]
[[File:Framerate.png|frame|center|Framerate for different resolutions on the CSC kernel.]]


=Execution time=
==Execution time==
These measurements were taken using some '''timestamps''' before and after the processing to measure just the execution time for the CSC kernel algorithm on each frame and hence avoiding possible false measurements from the GStreamer plugin. The image below shows the CSC execution time by each frame for each resolution.  
These measurements were taken using some '''timestamps''' before and after the processing to measure just the execution time for the CSC kernel algorithm on each frame and hence avoiding possible false measurements from the GStreamer plugin. The image below shows the CSC execution time by each frame for each resolution.  
[[File:Extime.png|frame|center|Execution time for different resolutions on the CSC kernel.]]
[[File:Extime.png|frame|center|Execution time for different resolutions on the CSC kernel.]]
583

edits

Cookies help us deliver our services. By using our services, you agree to our use of cookies.