|
|
| (10 intermediate revisions by 4 users not shown) |
| Line 1: |
Line 1: |
| − | <noinclude>
| + | #REDIRECT [https://developer.ridgerun.com/wiki/index.php?title=GStreamer_Based_Image_Signal_Processor/Performance/imx8 i.MX8 Performance] |
| − | {{GStreamer Based Image Signal Processor/Head|previous=Performance/Debayer|next=Contact Us|keywords=}}
| |
| − | </noinclude>
| |
| − | | |
| − | __TOC__
| |
| − | | |
| − | The following section describes some relevant performance measurements during the execution of the color space correction kernel for a few standard resolutions. It begins with a summary of the results detailed on the following sections, as well as the pipelines used to capture such results.
| |
| − | | |
| − | = Benchmarking =
| |
| − | | |
| − | == Pipeline ==
| |
| − | | |
| − | All the measurements below were made using the following minimal pipeline.
| |
| − | | |
| − | <pre style="background-color: khaki">
| |
| − | WIDTH=1920
| |
| − | HEIGHT=1080
| |
| − | | |
| − | gst-launch-1.0 videotestsrc is-live=true ! "video/x-raw,format=(string)RGBA,width=$WIDTH,height=$HEIGHT,framerate=(fraction)30/1" ! queue ! oclcsc ! fakesink -v
| |
| − | </pre>
| |
| − | | |
| − | == Summary ==
| |
| − | In this summary you can find measurements related with CPU usage, memory, execution time and maximum framerate supported by the debayer algorithm.
| |
| − | <html>
| |
| − | <center>
| |
| − | <table class="wikitable" style="text-align: center;">
| |
| − | <tr>
| |
| − | <th>Resolution</th>
| |
| − | <th>CPU usage (%) *</th>
| |
| − | <th>Memory (kB) *</th>
| |
| − | <th>Execution Time (ms)</th>
| |
| − | </tr>
| |
| − | <tr>
| |
| − | <td>640x480@30fps</td>
| |
| − | <td>4</td>
| |
| − | <td>19784</td>
| |
| − | <td>2.8</td>
| |
| − | </tr>
| |
| − | <tr>
| |
| − | <td>1280x720@30fps</td>
| |
| − | <td>10</td>
| |
| − | <td>20076</td>
| |
| − | <td>7.4</td>
| |
| − | </tr>
| |
| − | <tr>
| |
| − | <td>1920x1080@30fps</td>
| |
| − | <td>14</td>
| |
| − | <td>21140</td>
| |
| − | <td>16</td>
| |
| − | </tr>
| |
| − | <caption>Table 1. Summary table regarding to the debayer performance for several standard resolutions running at 30fps</caption>
| |
| − | </table>
| |
| − | </center>
| |
| − | </html>
| |
| − | | |
| − | | |
| − | <span style="color:magenta"> * To have in account: these values were taken with videotestsrc element and may decrease with a camera source capture. </span>
| |
| − | | |
| − | | |
| − | <html>
| |
| − | <center>
| |
| − | <table class="wikitable" style="text-align: center;">
| |
| − | <tr>
| |
| − | <th>Resolution</th>
| |
| − | <th>Maximum framerate (fps)</th>
| |
| − | </tr>
| |
| − | <tr>
| |
| − | <td>640x480</td>
| |
| − | <td>170</td>
| |
| − | </tr>
| |
| − | <tr>
| |
| − | <td>1280x720</td>
| |
| − | <td>63</td>
| |
| − | </tr>
| |
| − | <tr>
| |
| − | <td>1920x1080</td>
| |
| − | <td>29</td>
| |
| − | </tr>
| |
| − | <caption>Table 2. Summary table for the maximum framerate using debayer algorithm for several standard resolutions</caption>
| |
| − | </table>
| |
| − | </center>
| |
| − | </html>
| |
| − | | |
| − | =CPU usage=
| |
| − | These measurements were taken with '''top''' app to see the behavior of the pipeline while running, but we have to have in account that videotestsrc is used to generate the buffers and it consumes a lot of CPU.
| |
| − | [[File:Cpu.png|frame|center|CPU usage for CSC kernel.]]
| |
| − | | |
| − | =Memory usage=
| |
| − | These measurements were taken with '''meminfo''' file to see the behavior of the pipeline while running, 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.
| |
| − | [[File:Memo.png|frame|center|Memory consumption by CSC kernel.]]
| |
| − | | |
| − | =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.
| |
| − | [[File:Framerate.png|frame|center|Framerate for different resolutions on the CSC kernel.]]
| |
| − | | |
| − | =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.
| |
| − | [[File:Extime.png|frame|center|Execution time for different resolutions on the CSC kernel.]]
| |
| − | | |
| − | <noinclude>
| |
| − | {{GStreamer Based Image Signal Processor/Foot|Performance/Debayer|Contact Us}}
| |
| − | </noinclude>
| |
