Difference between revisions of "GStreamer Based Image Signal Processor/Performance/imx8"
(→Benchmark environment) |
m |
||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 3: | Line 3: | ||
</noinclude> | </noinclude> | ||
| − | = Benchmark environment = | + | == Benchmark environment == |
The following setup was used for all the benchmarks: | The following setup was used for all the benchmarks: | ||
| Line 11: | Line 11: | ||
*i.MX8 5640 RAW10 Camera Module | *i.MX8 5640 RAW10 Camera Module | ||
| − | == GStreamer Bayer10 Support == | + | === GStreamer Bayer10 Support === |
GStreamer has support for 8-bit Bayer only. To enable 10-bit Bayer support, please, follow this [[CUDA_ISP_for_NVIDIA_Jetson/Getting_Started/Building_custom_v4l2src_element|wiki]]. | GStreamer has support for 8-bit Bayer only. To enable 10-bit Bayer support, please, follow this [[CUDA_ISP_for_NVIDIA_Jetson/Getting_Started/Building_custom_v4l2src_element|wiki]]. | ||
| − | = CSC Benchmarking = | + | == 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 in the following sections, as well as the pipelines used to capture such results. | 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 in the following sections, as well as the pipelines used to capture such results. | ||
| − | == Pipeline == | + | === Pipeline === |
All the measurements below were made using the following minimal pipeline. | All the measurements below were made using the following minimal pipeline. | ||
| Line 30: | Line 30: | ||
</syntaxhighlight> | </syntaxhighlight> | ||
| − | == Summary == | + | === Summary === |
In this summary you can find measurements related with CPU usage, memory, execution time and maximum framerate supported by the CSC algorithm. | In this summary you can find measurements related with CPU usage, memory, execution time and maximum framerate supported by the CSC algorithm. | ||
<html> | <html> | ||
| Line 88: | Line 88: | ||
</html> | </html> | ||
| − | < | + | <br> |
| + | {{Ambox | ||
| + | |type=notice | ||
| + | |small=left | ||
| + | |issue='''Note:''' take into consideration that these values were taken using the videotestsrc element, and may decrease with a camera source capture. | ||
| + | |style=width:unset; | ||
| + | }} | ||
| + | <br> | ||
| − | ==CPU usage== | + | ===CPU usage=== |
These measurements were taken with the '''top''' app to monitor the behavior of the pipeline while running. | These measurements were taken with the '''top''' app to monitor the behavior of the pipeline while running. | ||
[[File:Cpu.png|frame|center|CPU usage for '''CSC''' element]] | [[File:Cpu.png|frame|center|CPU usage for '''CSC''' element]] | ||
| − | ==Memory usage== | + | ===Memory usage=== |
These measurements were taken with '''perf stat''' Linux tool to measure the bandwidth needed by the pipeline. | These measurements were taken with '''perf stat''' Linux tool to measure the bandwidth needed by the pipeline. | ||
[[File:Memo.png|frame|center|Memory bandwidth consumption by '''CSC''' element]] | [[File:Memo.png|frame|center|Memory bandwidth consumption by '''CSC''' element]] | ||
| − | ==Execution time== | + | ===Execution time=== |
These measurements were taken using some '''timestamps''' before and after the processing to measure just the execution time for the kernel algorithm on each frame and hence avoiding possible false measurements from the GStreamer plugin. | These measurements were taken using some '''timestamps''' before and after the processing to measure just the execution time for the kernel algorithm on each frame and hence avoiding possible false measurements from the GStreamer plugin. | ||
[[File:Extime.png|frame|center|Execution time for different resolutions with the '''CSC''' element]] | [[File:Extime.png|frame|center|Execution time for different resolutions with the '''CSC''' element]] | ||
| − | ==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. | 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. | ||
| Line 118: | Line 125: | ||
[[File:Framerate.png|frame|center|Framerate for different resolutions with the '''CSC''' element]] | [[File:Framerate.png|frame|center|Framerate for different resolutions with the '''CSC''' element]] | ||
| − | =Debayer Benckmarking= | + | ==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. | 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 == | + | === Pipeline === |
All the measurements below were made using the following minimal pipeline. | All the measurements below were made using the following minimal pipeline. | ||
| Line 130: | Line 137: | ||
HEIGHT=1080 | HEIGHT=1080 | ||
| − | $ gst-launch-1.0 v4l2src device=/dev/video0 ! video/x-bayer,format= | + | $ gst-launch-1.0 v4l2src device=/dev/video0 ! video/x-bayer,format=bggr,bpp=10,width=$WIDTH,height=$HEIGHT,framerate=30/1 ! ispclbayer10to8 ! queue ! ispcldebayer ! fakesink -v |
</syntaxhighlight> | </syntaxhighlight> | ||
| − | == Summary == | + | === Summary === |
In this summary you can find measurements related with CPU usage, memory, execution time and maximum framerate supported by the debayer algorithm. | In this summary you can find measurements related with CPU usage, memory, execution time and maximum framerate supported by the debayer algorithm. | ||
<html> | <html> | ||
| Line 192: | Line 199: | ||
</html> | </html> | ||
| − | < | + | <br> |
| + | {{Ambox | ||
| + | |type=notice | ||
| + | |small=left | ||
| + | |issue='''Note:''' take into consideration that these values were taken using the videotestsrc element, and may decrease with a camera source capture. | ||
| + | |style=width:unset; | ||
| + | }} | ||
| + | <br> | ||
| − | ==CPU usage== | + | ===CPU usage=== |
These measurements were taken with the '''top''' app to monitor the behavior of the pipeline while running. | These measurements were taken with the '''top''' app to monitor the behavior of the pipeline while running. | ||
| Line 200: | Line 214: | ||
| − | ==Memory usage== | + | ===Memory usage=== |
These measurements were taken with '''perf stat''' linux tool to measure the bandwidth needed by the pipeline. | These measurements were taken with '''perf stat''' linux tool to measure the bandwidth needed by the pipeline. | ||
[[File:memory-debayer.png|frame|center|Memory bandwidth consumption by '''debayer''' element]] | [[File:memory-debayer.png|frame|center|Memory bandwidth consumption by '''debayer''' element]] | ||
| − | ==Execution time== | + | ===Execution time=== |
These measurements were taken using some '''timestamps''' before and after the processing to measure just the execution time for the kernel algorithm on each frame and hence avoiding possible false measurements from the GStreamer plugin. | These measurements were taken using some '''timestamps''' before and after the processing to measure just the execution time for the kernel algorithm on each frame and hence avoiding possible false measurements from the GStreamer plugin. | ||
| Line 211: | Line 225: | ||
| − | ==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. | 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. | ||
| Line 225: | Line 239: | ||
[[File:max-framerate-debayer.png|frame|center|Framerate for different resolutions with the '''debayer''' element]] | [[File:max-framerate-debayer.png|frame|center|Framerate for different resolutions with the '''debayer''' element]] | ||
| − | = AWB Benchmarking = | + | == 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. | 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 == | + | === Pipeline === |
All the measurements below were made using the following minimal pipeline. | All the measurements below were made using the following minimal pipeline. | ||
| Line 237: | Line 251: | ||
$ HEIGHT=1080 | $ HEIGHT=1080 | ||
| − | $ gst-launch-1.0 v4l2src device=/dev/video0 ! video/x-bayer,format= | + | $ gst-launch-1.0 v4l2src device=/dev/video0 ! video/x-bayer,format=bggr,bpp=10,width=$WIDTH,height=$HEIGHT,framerate=30/1 ! ispclbayer10to8 ! queue ! ispclawb ! fakesink -v |
</syntaxhighlight> | </syntaxhighlight> | ||
| − | == Summary == | + | === 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. | In this summary you can find measurements related with CPU usage, memory, execution time and maximum framerate supported by the auto-white balance algorithm. | ||
<html> | <html> | ||
| Line 299: | Line 313: | ||
</html> | </html> | ||
| − | < | + | <br> |
| + | {{Ambox | ||
| + | |type=notice | ||
| + | |small=left | ||
| + | |issue='''Note:''' take into consideration that these values were taken using the videotestsrc element, and may decrease with a camera source capture. | ||
| + | |style=width:unset; | ||
| + | }} | ||
| + | <br> | ||
| − | ==CPU usage== | + | ===CPU usage=== |
These measurements were taken with the '''top''' app to monitor the behavior of the pipeline while running. | These measurements were taken with the '''top''' app to monitor the behavior of the pipeline while running. | ||
[[File:CPU usage for AWB.png|frame|center|CPU usage for '''AWB''' element]] | [[File:CPU usage for AWB.png|frame|center|CPU usage for '''AWB''' element]] | ||
| − | ==Memory usage== | + | ===Memory usage=== |
These measurements were taken with '''perf stat''' linux tool to measure the bandwidth needed by the pipeline. | These measurements were taken with '''perf stat''' linux tool to measure the bandwidth needed by the pipeline. | ||
[[File:Memory Bandwidth for AWB.png|frame|center|Memory bandwidth consumption by '''AWB''' element]] | [[File:Memory Bandwidth for AWB.png|frame|center|Memory bandwidth consumption by '''AWB''' element]] | ||
| − | ==Execution time== | + | ===Execution time=== |
These measurements were taken using some '''timestamps''' before and after the processing to measure just the execution time for the kernel algorithm on each frame and hence avoiding possible false measurements from the GStreamer plugin. | These measurements were taken using some '''timestamps''' before and after the processing to measure just the execution time for the kernel algorithm on each frame and hence avoiding possible false measurements from the GStreamer plugin. | ||
| Line 317: | Line 338: | ||
| − | ==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. | 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. | ||
| Line 330: | Line 351: | ||
[[File:Maximum Framerate AWB.png|frame|center|Framerate for different resolutions with the '''AWB''' element]] | [[File:Maximum Framerate AWB.png|frame|center|Framerate for different resolutions with the '''AWB''' element]] | ||
| − | = Histogram Equalization Benchmarking = | + | == 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. | 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 == | + | === Pipeline === |
All the measurements below were made using the following minimal pipeline. | All the measurements below were made using the following minimal pipeline. | ||
| Line 342: | Line 363: | ||
$ HEIGHT=1080 | $ HEIGHT=1080 | ||
| − | $ gst-launch-1.0 v4l2src device=/dev/video0 ! video/x-bayer,format= | + | $ gst-launch-1.0 v4l2src device=/dev/video0 ! video/x-bayer,format=bggr,bpp=10,width=$WIDTH,height=$HEIGHT,framerate=30/1 ! ispclbayer10to8 ! queue ! ispcleq ! fakesink -v |
</syntaxhighlight> | </syntaxhighlight> | ||
| − | == Summary == | + | === Summary === |
In this summary you can find measurements related with CPU usage, memory, execution time and maximum framerate supported by the Histogram Equalization algorithm. | In this summary you can find measurements related with CPU usage, memory, execution time and maximum framerate supported by the Histogram Equalization algorithm. | ||
<html> | <html> | ||
| Line 404: | Line 425: | ||
</html> | </html> | ||
| − | < | + | <br> |
| + | {{Ambox | ||
| + | |type=notice | ||
| + | |small=left | ||
| + | |issue='''Note:''' take into consideration that these values were taken using the videotestsrc element, and may decrease with a camera source capture. | ||
| + | |style=width:unset; | ||
| + | }} | ||
| + | <br> | ||
| − | ==CPU usage== | + | ===CPU usage=== |
These measurements were taken with the '''top''' app to monitor the behavior of the pipeline while running. | These measurements were taken with the '''top''' app to monitor the behavior of the pipeline while running. | ||
[[File:CPU usage Eq.png|frame|center|CPU usage for '''Histogram Equalization''' element]] | [[File:CPU usage Eq.png|frame|center|CPU usage for '''Histogram Equalization''' element]] | ||
| − | ==Memory usage== | + | ===Memory usage=== |
These measurements were taken with '''perf stat''' linux tool to measure the bandwidth needed by the pipeline. | These measurements were taken with '''perf stat''' linux tool to measure the bandwidth needed by the pipeline. | ||
[[File:Memory Bandwidth Eq.png|frame|center|Memory bandwidth consumption by '''Histogram Equalization''' element]] | [[File:Memory Bandwidth Eq.png|frame|center|Memory bandwidth consumption by '''Histogram Equalization''' element]] | ||
| − | ==Execution time== | + | ===Execution time=== |
These measurements were taken using some '''timestamps''' before and after the processing to measure just the execution time for the kernel algorithm on each frame and hence avoiding possible false measurements from the GStreamer plugin. | These measurements were taken using some '''timestamps''' before and after the processing to measure just the execution time for the kernel algorithm on each frame and hence avoiding possible false measurements from the GStreamer plugin. | ||
[[File:Execution Time Equalizer.png|frame|center|Execution time for different resolutions with the '''Histogram Equalization''' element]] | [[File:Execution Time Equalizer.png|frame|center|Execution time for different resolutions with the '''Histogram Equalization''' element]] | ||
| − | ==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. | 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. | ||
Latest revision as of 13:09, 22 July 2023
| GStreamer Image Signal Processor | |
|---|---|
 | |
| Image Signal Processor Basics | |
|
|
|
| Docs | |
|
|
|
| Getting Started | |
|
|
|
| Examples | |
|
|
|
| Performance | |
|
|
|
| Troubleshoot | |
| Contact Us |
Contents
Benchmark environment
The following setup was used for all the benchmarks:
- NXP® i.MX 8MQuad Evaluation Kit (EVK)
- Yocto built image (fsl-image-multimedia) from Freescale BSP
- i.MX8 5640 RAW10 Camera Module
GStreamer Bayer10 Support
GStreamer has support for 8-bit Bayer only. To enable 10-bit Bayer support, please, follow this wiki.
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 in 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 Bandwidth (GHz) | Execution Time (ms) |
|---|---|---|---|
| 640x480@30fps | 4 | 1.020 | 2.24 |
| 1280x720@30fps | 10 | 1.034 | 6.19 |
| 1920x1080@30fps | 14 | 1.466 | 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 the top app to monitor the behavior of the pipeline while running.
Error creating thumbnail: Unable to save thumbnail to destination
CPU usage for CSC element
Memory usage
These measurements were taken with perf stat Linux tool to measure the bandwidth needed by the pipeline.
Error creating thumbnail: Unable to save thumbnail to destination
Memory bandwidth consumption by CSC element
Execution time
These measurements were taken using some timestamps before and after the processing to measure just the execution time for the kernel algorithm on each frame and hence avoiding possible false measurements from the GStreamer plugin.
Error creating thumbnail: Unable to save thumbnail to destination
Execution time for different resolutions with the CSC element
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 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
Error creating thumbnail: Unable to save thumbnail to destination
Framerate for different resolutions with the CSC element
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 device=/dev/video0 ! video/x-bayer,format=bggr,bpp=10,width=$WIDTH,height=$HEIGHT,framerate=30/1 ! ispclbayer10to8 ! queue ! 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 Bandwidth (GHz) | Execution Time (ms) |
|---|---|---|---|
| 640x480@30fps | 2 | 1.025 | 3.54 |
| 1280x720@30fps | 2 | 1.084 | 9.89 |
| 1920x1080@30fps | 3 | 1.402 | 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 the top app to monitor the behavior of the pipeline while running.
Error creating thumbnail: Unable to save thumbnail to destination
CPU usage for debayer element
Memory usage
These measurements were taken with perf stat linux tool to measure the bandwidth needed by the pipeline.
Error creating thumbnail: Unable to save thumbnail to destination
Memory bandwidth consumption by debayer element
Execution time
These measurements were taken using some timestamps before and after the processing to measure just the execution time for the kernel algorithm on each frame and hence avoiding possible false measurements from the GStreamer plugin.
Error creating thumbnail: Unable to save thumbnail to destination
Execution time for different resolutions with the debayer element
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 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-bayer,format=bggr,width=$WIDTH,height=$HEIGHT,framerate=30/1" ! queue ! ispcldebayer ! perf ! fakesink -v
Error creating thumbnail: Unable to save thumbnail to destination
Framerate for different resolutions with the debayer element
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 v4l2src device=/dev/video0 ! video/x-bayer,format=bggr,bpp=10,width=$WIDTH,height=$HEIGHT,framerate=30/1 ! ispclbayer10to8 ! 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 Bandwidth (GHz) | Execution Time (ms) |
|---|---|---|---|
| 640x480@30fps | 10 | 0.994 | 3.11 |
| 1280x720@30fps | 12 | 1.032 | 4.54 |
| 1920x1080@30fps | 16 | 1.239 | 8.52 |
| Resolution | Maximum framerate (fps) * |
|---|---|
| 640x480 | 365 |
| 1280x720 | 135 |
| 1920x1080 | 62 |
| 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 the top app to monitor the behavior of the pipeline while running.
Error creating thumbnail: Unable to save thumbnail to destination
CPU usage for AWB element
Memory usage
These measurements were taken with perf stat linux tool to measure the bandwidth needed by the pipeline.
Error creating thumbnail: Unable to save thumbnail to destination
Memory bandwidth consumption by AWB element
Execution time
These measurements were taken using some timestamps before and after the processing to measure just the execution time for the kernel algorithm on each frame and hence avoiding possible false measurements from the GStreamer plugin.
Error creating thumbnail: Unable to save thumbnail to destination
Execution time for different resolutions with the AWB element
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 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-bayer,format=bggr,width=$WIDTH,height=$HEIGHT,framerate=30/1" ! queue ! ispclawb ! perf ! fakesink -v
Error creating thumbnail: Unable to save thumbnail to destination
Framerate for different resolutions with the AWB element
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 v4l2src device=/dev/video0 ! video/x-bayer,format=bggr,bpp=10,width=$WIDTH,height=$HEIGHT,framerate=30/1 ! ispclbayer10to8 ! 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 Bandwidth (GHz) | Execution Time (ms) |
|---|---|---|---|
| 640x480@30fps | 10 | 0.990 | 4.28 |
| 1280x720@30fps | 12 | 1.047 | 6.07 |
| 1920x1080@30fps | 16 | 1.277 | 10.95 |
| Resolution | Maximum framerate (fps)* |
|---|---|
| 640x480 | 345 |
| 1280x720 | 135 |
| 1920x1080 | 62 |
| 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 the top app to monitor the behavior of the pipeline while running.
Error creating thumbnail: Unable to save thumbnail to destination
CPU usage for Histogram Equalization element
Memory usage
These measurements were taken with perf stat linux tool to measure the bandwidth needed by the pipeline.
Error creating thumbnail: Unable to save thumbnail to destination
Memory bandwidth consumption by Histogram Equalization element
Execution time
These measurements were taken using some timestamps before and after the processing to measure just the execution time for the kernel algorithm on each frame and hence avoiding possible false measurements from the GStreamer plugin.
Error creating thumbnail: Unable to save thumbnail to destination
Execution time for different resolutions with the Histogram Equalization element
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 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-bayer,format=bggr,width=$WIDTH,height=$HEIGHT,framerate=30/1" ! queue ! ispcleq ! perf ! fakesink -v
Error creating thumbnail: Unable to save thumbnail to destination
Framerate for different resolutions with the Histogram Equalization element
