GStreamer Based Image Signal Processor - Performance - Debayer
| GStreamer Image Signal Processor | |
|---|---|
 | |
| Image Signal Processor Basics | |
|
|
|
| Docs | |
|
|
|
| Getting Started | |
|
|
|
| Examples | |
|
|
|
| Performance | |
|
|
|
| Troubleshoot | |
| Contact Us |
Contents
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.
Summary
Benchmarking for i.MX8
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-bayer, format=(string)bggr, width=$WIDTH, height=$HEIGHT,framerate=(fraction)30/1" ! 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 (kB) * | Execution Time (ms) |
|---|---|---|---|
| 640x480@30fps | 8 | 17980 | 3.54 |
| 1280x720@30fps | 9 | 18800 | 9.82 |
| 1920x1080@30fps | 14 | 19896 | 21.19 |
Note: take into consideration that these values were taken using the videotestsrc element, and may decrease with a camera source capture.
| Resolution | Maximum framerate (fps) |
|---|---|
| 640x480 | 266 |
| 1280x720 | 101 |
| 1920x1080 | 46 |
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.
