Difference between revisions of "GstRtspSink - NVidia TX1 EVM"
m |
m |
||
| Line 1: | Line 1: | ||
{{GstRtspSink/Head|previous=NVidia TX2|next=iMX6_Nitrogen|keywords=}} | {{GstRtspSink/Head|previous=NVidia TX2|next=iMX6_Nitrogen|keywords=}} | ||
| + | <table> | ||
| + | <tr> | ||
| + | <td><div class="clear; float:right">__TOC__</div></td> | ||
| + | <td valign=top> | ||
{{GStreamer debug}} | {{GStreamer debug}} | ||
| + | </td> | ||
| + | </table> | ||
<br> | <br> | ||
| Line 20: | Line 26: | ||
</syntaxhighlight> | </syntaxhighlight> | ||
| + | <!----- | ||
<pre style="background:yellow"> | <pre style="background:yellow"> | ||
The perf element is optional and its only used to print frame rate and CPU usage. If you are interested in using it, you may find it at https://github.com/RidgeRun/gst-perf | The perf element is optional and its only used to print frame rate and CPU usage. If you are interested in using it, you may find it at https://github.com/RidgeRun/gst-perf | ||
</pre> | </pre> | ||
| − | + | ----> | |
| − | + | {{Ambox | |
| + | |type=notice | ||
| + | |small=left | ||
| + | |issue=The perf element is optional and its only used to print frame rate and CPU usage. If you are interested in using it, you may find it at https://github.com/RidgeRun/gst-perf. | ||
| + | }} | ||
== Framerate == | == Framerate == | ||
Revision as of 10:10, 16 April 2020
Contents |
|
This wiki presents some performance measurements of a typical GstRtspSink pipeline on the NVidia TX1 EVM.
GstRtspSink Pipeline
The following GstRtspSink pipeline captures images from the IMX219 Sony sensor, encodes it using HW accelerated H264 encoder and streams it using GstRtspSink.
PORT=5000
MAPPING=/stream1
gst-launch-1.0 nvcamerasrc sensor-id=0 ! omxh264enc control-rate=2 bitrate=4000000 ! \
'video/x-h264, stream-format=(string)byte-stream' ! h264parse ! video/x-h264, mapping=${MAPPING} ! \
perf ! rtspsink service=${PORT}
 | The perf element is optional and its only used to print frame rate and CPU usage. If you are interested in using it, you may find it at https://github.com/RidgeRun/gst-perf. |
Framerate
The frame rate was measured using the perf element.
Timestamp: 3:59:14.941918568; Bps: 28443; fps: 30.3 Timestamp: 3:59:15.943461170; Bps: 32116; fps: 29.97 Timestamp: 3:59:16.949348157; Bps: 27899; fps: 29.85 Timestamp: 3:59:17.953943021; Bps: 29440; fps: 29.88 Timestamp: 3:59:18.959193504; Bps: 28735; fps: 29.85 Timestamp: 3:59:19.960098613; Bps: 25735; fps: 30.0 Timestamp: 3:59:20.965807217; Bps: 27132; fps: 29.85 Timestamp: 3:59:21.967152009; Bps: 27030; fps: 29.97
CPU Load
The CPU load was measured using tetrastats.
RAM 1016/3994MB (lfb 475x4MB) cpu [40%,12%,14%,25%]@307 GR3D 0%@76 EDP limit 0 RAM 1016/3994MB (lfb 475x4MB) cpu [37%,18%,12%,32%]@307 GR3D 0%@76 EDP limit 0 RAM 1016/3994MB (lfb 475x4MB) cpu [38%,19%,22%,26%]@204 GR3D 0%@76 EDP limit 0 RAM 1016/3994MB (lfb 475x4MB) cpu [34%,35%,18%,10%]@307 GR3D 0%@76 EDP limit 0 RAM 1016/3994MB (lfb 475x4MB) cpu [33%,34%,18%,29%]@204 GR3D 0%@76 EDP limit 0 RAM 1016/3994MB (lfb 475x4MB) cpu [19%,27%,23%,38%]@307 GR3D 0%@76 EDP limit 0 RAM 1016/3994MB (lfb 475x4MB) cpu [32%,30%,13%,32%]@204 GR3D 0%@76 EDP limit 0
