GstRtspSink - NVidia TX1 EVM: Difference between revisions

From RidgeRun Developer Wiki
mNo edit summary
No edit summary
 
(13 intermediate revisions by 3 users not shown)
Line 1: Line 1:
<seo title="GstRtspSink Pipeline | NVidia TX1 EVM | RidgeRun Developer" titlemode="replace" keywords="GStreamer, Linux SDK, Linux BSP,  Embedded Linux, Device Drivers, Nvidia, Jetson, TX1, TX2, Xilinx, TI, NXP, Freescale, Embedded Linux driver development, Linux Software development, Embedded Linux SDK, Embedded Linux Application development, GStreamer Multimedia Framework."  description="Read about the GstRtspSink Pipelines in this breakdown of the NVidia TX1 EVM. Learn more about performance measurements of GstRtspSink now at RidgeRun Developer."></seo>


This wiki presents some performance measurements of a typical GstRtspSink pipeline on the NVidia TX1 EVM.
<br>
<table>
<table>
<tr>
<tr>
<td><div class="clear; float:right">__TOC__</div></td>
<td><div class="clear; float:right">__TOC__</div></td>
<td valign=top>
<td valign=top>
{{Debug Symbol}} Problems running the pipelines shown on this page?<br>Please see our [http://developer.ridgerun.com/wiki/index.php?title=GStreamer_Debugging GStreamer Debugging guide] for help.
<td>
{{GStreamer debug}}  
</td>
<td>
{{NVIDIA Preferred Partner logo}}
</td>
<td>
{{ContactUs Button}}
</td>
</td>
</table>
</table>
 
<br>
{{GstRtspSink Page|
[[GstRtspSink - Performance|Performance]]|
[[GstRtspSink_-_iMX6_Nitrogen|iMX6 Nitrogen]]|
 
This wiki presents some performance measurements of a typical GstRtspSink pipeline on the NVidia TX1 EVM.
 
__TOC__


== GstRtspSink Pipeline ==
== 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.
The following [https://www.ridgerun.com/gst-multistream-rtspserver GstRtspSink] pipeline captures images from the IMX219 Sony sensor, encodes it using HW accelerated H264 encoder, and streams it using GstRtspSink.


<syntaxhighlight lang=bash>
<syntaxhighlight lang=bash>
Line 25: Line 27:
MAPPING=/stream1
MAPPING=/stream1


gst-launch-1.0 nvcamerasrc sensor-id=0 ! omxh264enc control-rate=2 bitrate=4000000 ! 'video/x-h264, stream-format=(string) \
gst-launch-1.0 nvcamerasrc sensor-id=0 ! omxh264enc control-rate=2 bitrate=4000000 ! \
byte-stream' ! h264parse  ! video/x-h264, mapping=${MAPPING} ! perf ! rtspsink service=5000
  'video/x-h264, stream-format=(string)byte-stream' ! h264parse  ! video/x-h264, mapping=${MAPPING} ! \
  perf ! rtspsink service=${PORT}
</syntaxhighlight>
</syntaxhighlight>


{{Ambox
|type=notice
|small=left
|issue='''The [https://github.com/RidgeRun/gst-perf perf element] is optional.  The perf element prints frame rate and CPU usage debug information.'''
|style=width:unset;
}}


== Framerate ==
== Framerate ==
Line 44: Line 53:
Timestamp: 3:59:21.967152009; Bps: 27030; fps: 29.97
Timestamp: 3:59:21.967152009; Bps: 27030; fps: 29.97
</pre>
</pre>


== CPU Load ==
== CPU Load ==
Line 59: Line 67:
RAM 1016/3994MB (lfb 475x4MB) cpu [32%,30%,13%,32%]@204 GR3D 0%@76 EDP limit 0
RAM 1016/3994MB (lfb 475x4MB) cpu [32%,30%,13%,32%]@204 GR3D 0%@76 EDP limit 0
</pre>
</pre>
}}

Latest revision as of 21:04, 26 April 2024


This wiki presents some performance measurements of a typical GstRtspSink pipeline on the NVidia TX1 EVM.

Problems running the pipelines shown on this page? Please see our GStreamer Debugging guide for help.


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}

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