Difference between revisions of "GStreamer Based Image Signal Processor/Performance/imx8"
| Line 314: | Line 314: | ||
</syntaxhighlight> | </syntaxhighlight> | ||
| − | [[File: | + | [[File:Maximum Framerate AWB.png|frame|center|Maximum framerate debayering for different resolutions.]] |
| + | |||
= Histogram Equalization Benchmarking = | = Histogram Equalization Benchmarking = | ||
| Line 375: | Line 376: | ||
<tr> | <tr> | ||
<td>640x480</td> | <td>640x480</td> | ||
| − | <td> </td> | + | <td> 196 </td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>1280x720</td> | <td>1280x720</td> | ||
| − | <td> </td> | + | <td> 95 </td> |
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>1920x1080</td> | <td>1920x1080</td> | ||
| − | <td> </td> | + | <td> 43 </td> |
</tr> | </tr> | ||
<caption>Table 2. Summary table for the maximum framerate using Histogram Equalization algorithm for several standard resolutions</caption> | <caption>Table 2. Summary table for the maximum framerate using Histogram Equalization algorithm for several standard resolutions</caption> | ||
| Line 418: | Line 419: | ||
</syntaxhighlight> | </syntaxhighlight> | ||
| − | [[File: | + | [[File:Maximum Framerate Eq.png|frame|center|Maximum framerate debayering for different resolutions.]] |
<noinclude> | <noinclude> | ||
{{GStreamer Based Image Signal Processor/Foot|Performance/imx6|Performance/Color Space Conversion}} | {{GStreamer Based Image Signal Processor/Foot|Performance/imx6|Performance/Color Space Conversion}} | ||
</noinclude> | </noinclude> | ||
Revision as of 12:00, 17 September 2019
| GStreamer Image Signal Processor | |
|---|---|
 | |
| Image Signal Processor Basics | |
|
|
|
| Docs | |
|
|
|
| Getting Started | |
|
|
|
| Examples | |
|
|
|
| Performance | |
|
|
|
| Troubleshoot | |
| Contact Us |
Contents
CSC Benchmarking
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 the results detailed on the following sections, as well as the pipelines used to capture such results.
Pipeline
All the measurements below were made using the following minimal pipeline.
$ 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 ! ispclcsc ! fakesink -v
Summary
In this summary you can find measurements related with CPU usage, memory, execution time and maximum framerate supported by the CSC algorithm.
| Resolution | CPU usage (%) | Memory (kB) | Execution Time (ms) |
|---|---|---|---|
| 640x480@30fps | 4 | 18664 | 2.24 |
| 1280x720@30fps | 10 | 19484 | 6.19 |
| 1920x1080@30fps | 14 | 21424 | 13.17 |
| Resolution | Maximum framerate (fps) * |
|---|---|
| 640x480 | 333 |
| 1280x720 | 120 |
| 1920x1080 | 55 |
*Note: take into consideration that these values were taken using the videotestsrc element, and may decrease with a camera source capture.
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.
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.
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.
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.
The following pipeline was used to test the maximum framerate, please note the use of videotestsrc.
$ WIDTH=1920
$ HEIGHT=1080
$ gst-launch-1.0 videotestsrc ! "video/x-raw,format=(string)RGBA,width=$WIDTH,height=$HEIGHT,framerate=(fraction)30/1" ! queue ! ispclcsc ! fakesink -v
Debayer Benckmarking
The following section describes some relevant performance measurements during debayering 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.
Pipeline
All the measurements below were made using the following minimal pipeline.
WIDTH=1920
HEIGHT=1080
gst-launch-1.0 v4l2src io-mode=userptr device=/dev/video1 ! video/x-bayer,width=$WIDTH,height=$HEIGHT,framerate=30/1 ! ispcldebayer ! fakesink -v
Summary
In this summary you can find measurements related with CPU usage, memory, execution time and maximum framerate supported by the debayer algorithm.
| Resolution | CPU usage (%) | Memory (kB) | Execution Time (ms) |
|---|---|---|---|
| 640x480@30fps | 2 | 20084 | 3.54 |
| 1280x720@30fps | 2 | 22564 | 9.89 |
| 1920x1080@30fps | 3 | 23212 | 21.46 |
| Resolution | Maximum framerate (fps)* |
|---|---|
| 640x480 | 266 |
| 1280x720 | 101 |
| 1920x1080 | 46 |
*Note: take into consideration that these values were taken using the videotestsrc element, and may decrease with a camera source capture.
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.
$ 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
AWB Benchmarking
The following section describes some relevant performance measurements for the auto-white balance 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.
Pipeline
All the measurements below were made using the following minimal pipeline.
$ 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 ! ispclawb ! fakesink -v
Summary
In this summary you can find measurements related with CPU usage, memory, execution time and maximum framerate supported by the auto-white balance algorithm.
| Resolution | CPU usage (%) | Memory (kB) | Execution Time (ms) |
|---|---|---|---|
| 640x480@30fps | |||
| 1280x720@30fps | |||
| 1920x1080@30fps |
| Resolution | Maximum framerate (fps) * |
|---|---|
| 640x480 | 230 |
| 1280x720 | 96 |
| 1920x1080 | 44 |
*Note: take into consideration that these values were taken using the videotestsrc element, and may decrease with a camera source capture.
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.
$ 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
Histogram Equalization Benchmarking
The following section describes some relevant performance measurements for the Histogram Equalization 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.
Pipeline
All the measurements below were made using the following minimal pipeline.
$ 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 ! ispcleq ! fakesink -v
Summary
In this summary you can find measurements related with CPU usage, memory, execution time and maximum framerate supported by the Histogram Equalization algorithm.
| Resolution | CPU usage (%) | Memory (kB) | Execution Time (ms) |
|---|---|---|---|
| 640x480@30fps | |||
| 1280x720@30fps | |||
| 1920x1080@30fps |
| Resolution | Maximum framerate (fps)* |
|---|---|
| 640x480 | 196 |
| 1280x720 | 95 |
| 1920x1080 | 43 |
*Note: take into consideration that these values were taken using the videotestsrc element, and may decrease with a camera source capture.
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.
$ 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
