Difference between revisions of "NVIDIA Jetson Orin/GStreamer Pipelines/Capture and Display"
(→Performance) |
(→Performance) |
||
| Line 29: | Line 29: | ||
'''FPS:''' | '''FPS:''' | ||
| − | * For the FPS, the [https://github.com/RidgeRun/gst-perf RidgeRun gst-perf plugin] is used. This plugin computes the FPS means. | + | * For the FPS, the [https://github.com/RidgeRun/gst-perf RidgeRun gst-perf plugin] is used. This plugin computes the FPS means. For the measurement, we compute the average over 30 samples of the FPS means values. |
{{Review| Reword |jcaballero}} | {{Review| Reword |jcaballero}} | ||
Revision as of 11:21, 19 May 2022
 | NVIDIA Jetson Orin RidgeRun documentation is currently under development. |
|
USB capture
 | jcaballero: Reword this. For this section the USB camera LI-10635 was used.or something similar. Please use xvimagesink sync false (please remove this box when addressed) |
For this section the USB camera LI-10635 was used. The following GStreamer pipeline is used:
DISPLAY=:0 GST_DEBUG=2 gst-launch-1.0 -v v4l2src device=/dev/video0 ! video/x-raw,framerate=30/1,width=1280,height=720 ! nvvidconv ! xvimagesink
Use the following command to get the value of the DISPLAY variable:
echo $DISPLAY
Performance
With the pipeline running, we took the following measurements:
CPU usage:
- For the CPU percentage utilization, the tegrastats utility is used as follows:
sudo tegrastats -readall. This command shows the percentage utilization of the 12 cores that the Jetson AGX Orin devkit has. For the measurement, we compute the average over 30 samples of the utilization values for the CPU cores.
| jcaballero: Reword: For the measurement, we compute the average over 30 samples of the utilization values for the CPU cores. (please remove this box when addressed) |
GPU Usage:
- The same is done in the case of GPU percentage. The board has 2 GPUs. So, 30 values of each one are taken, and then, the average is obtained.
FPS:
- For the FPS, the RidgeRun gst-perf plugin is used. This plugin computes the FPS means. For the measurement, we compute the average over 30 samples of the FPS means values.
| jcaballero: Reword (please remove this box when addressed) |
Latency:
- In the case of the Latency parameter, the RidgeRun GstShark plugin is used. For this measurement, it is important to take into account that the measurement is not a glass to glass calculation. What GstShark does is give the time needed by a buffer for travel from the source pad of the source element to the source pad of the remaining elements of the pipeline.
| Operation Mode | CPU (%) | GPU 1 (%) | GPU 2 (%) | FPS | Latency (ms) |
|---|---|---|---|---|---|
| 0 (max performance, default) | 28,2 | 26,83 | 23,93 | 30,01 | 0,10 |
| 1 (min power) | 26,93 | 7,26 | 52,4 | 26,57 | 0.16 |
| 2 (30W) | 21.4 | 5.97 | 62.67 | 21.91 | 0.16 |
To change the operation mode see the Performance Tuning - Tuning Power section.
