583
edits
GStreamer Based Image Signal Processor/Performance/imx8: Difference between revisions
GStreamer Based Image Signal Processor/Performance/imx8 (view source)
Revision as of 16:51, 17 September 2019
, 17 September 2019no edit summary
No edit summary |
|||
| Line 210: | Line 210: | ||
[[File:max-framerate-debayer.png|frame|center|Maximum framerate debayering for different resolutions.]] | [[File:max-framerate-debayer.png|frame|center|Maximum framerate debayering for different resolutions.]] | ||
| Line 275: | Line 271: | ||
<tr> | <tr> | ||
<td>640x480</td> | <td>640x480</td> | ||
<td> </td> | <td> 230 </td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>1280x720</td> | <td>1280x720</td> | ||
<td> </td> | <td> 96 </td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>1920x1080</td> | <td>1920x1080</td> | ||
<td> </td> | <td> 44 </td> | ||
</tr> | </tr> | ||
<caption>Table 2. Summary table for the maximum framerate using AWB algorithm for several standard resolutions</caption> | <caption>Table 2. Summary table for the maximum framerate using AWB algorithm for several standard resolutions</caption> | ||
| Line 291: | Line 287: | ||
<span style="color:red"> '''*Note:''' take into consideration that these values were taken using the videotestsrc element, and may decrease with a camera source capture. </span> | <span style="color:red"> '''*Note:''' take into consideration that these values were taken using the videotestsrc element, and may decrease with a camera source capture. </span> | ||
==CPU usage== | |||
These measurements were taken with '''top''' app to see the behavior of the pipeline while running at 30fps, but we have to have in account that videotestsrc is used to generate the buffers and it consumes a lot of CPU. | |||
==Memory usage== | |||
These measurements were taken with '''meminfo''' file to see the behavior of the pipeline while running at 30fps, but we have to have in account that videotestsrc is used to generate the buffers and it depends on the framerate due to the number of buffers generated by videotestsrc. | |||
==Execution time== | |||
These measurements were taken putting some '''timestamps''' before and after the processing to measure just the execution time for the debayer kernel algorithm by each frame and avoiding possible false measurements from the GStreamer plugin. The image below shows the debayer execution time by each frame for each resolution. | |||
==Maximum Framerate== | |||
These measurements were taken with '''gstperf''' tool to see the behavior of the pipeline while running, with videotestsrc we are able to push buffers as much as possible to the element. The image below shows the maximum framerate that the debayer element supports. It depends on the execution time of the debayer kernel algorithm. | |||
The following pipeline was used to test the maximum framerate, please note the use of videotestsrc. | |||
<syntaxhighlight lang=bash style="background-color: #f0fff0"> | |||
$ WIDTH=1920 | |||
$ HEIGHT=1080 | |||
$ gst-launch-1.0 videotestsrc ! "video/x-raw,format=(string)RGBA,width=$WIDTH,height=$HEIGHT,framerate=(fraction)30/1" ! queue ! ispcldebayer ! fakesink -v | |||
</syntaxhighlight> | |||
[[File:max-framerate-debayer.png|frame|center|Maximum framerate debayering for different resolutions.]] | |||
= Histogram Equalization Benchmarking = | = Histogram Equalization Benchmarking = | ||
| Line 367: | Line 391: | ||
<span style="color:red"> '''*Note:''' take into consideration that these values were taken using the videotestsrc element, and may decrease with a camera source capture. </span> | <span style="color:red"> '''*Note:''' take into consideration that these values were taken using the videotestsrc element, and may decrease with a camera source capture. </span> | ||
==CPU usage== | |||
These measurements were taken with '''top''' app to see the behavior of the pipeline while running at 30fps, but we have to have in account that videotestsrc is used to generate the buffers and it consumes a lot of CPU. | |||
==Memory usage== | |||
These measurements were taken with '''meminfo''' file to see the behavior of the pipeline while running at 30fps, but we have to have in account that videotestsrc is used to generate the buffers and it depends on the framerate due to the number of buffers generated by videotestsrc. | |||
==Execution time== | |||
These measurements were taken putting some '''timestamps''' before and after the processing to measure just the execution time for the debayer kernel algorithm by each frame and avoiding possible false measurements from the GStreamer plugin. The image below shows the debayer execution time by each frame for each resolution. | |||
==Maximum Framerate== | |||
These measurements were taken with '''gstperf''' tool to see the behavior of the pipeline while running, with videotestsrc we are able to push buffers as much as possible to the element. The image below shows the maximum framerate that the debayer element supports. It depends on the execution time of the debayer kernel algorithm. | |||
The following pipeline was used to test the maximum framerate, please note the use of videotestsrc. | |||
<syntaxhighlight lang=bash style="background-color: #f0fff0"> | |||
$ WIDTH=1920 | |||
$ HEIGHT=1080 | |||
$ gst-launch-1.0 videotestsrc ! "video/x-raw,format=(string)RGBA,width=$WIDTH,height=$HEIGHT,framerate=(fraction)30/1" ! queue ! ispcldebayer ! fakesink -v | |||
</syntaxhighlight> | |||
[[File:max-framerate-debayer.png|frame|center|Maximum framerate debayering for different resolutions.]] | |||
<noinclude> | |||
{{GStreamer Based Image Signal Processor/Foot|Performance/imx6|Performance/Color Space Conversion}} | |||
</noinclude> | |||