Difference between revisions of "GstRtspSink - NVidia TX2"

From RidgeRun Developer Connection
Jump to: navigation, search
Line 34: Line 34:
 
The CPU load was measured using tetrastats.
 
The CPU load was measured using tetrastats.
  
<pre>
+
[[File:Cpu usage.png|thumb|CPU measured]]
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
 
</pre>
 
 
}}
 
}}

Revision as of 11:35, 3 March 2020


Performance


Home

NVidia TX1 EVM



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


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

GstRtspSink Pipeline

The following GstRtspSink pipeline generates video with a videotestsrc, encodes it using HW accelerated H264 encoder and streams it using GstRtspSink.

PORT=5000
MAPPING=/stream1
gst-launch-1.0 videotestsrc ! omxh264enc ! h264parse ! video/x-h264, mapping=${MAPPING}  ! perf print-arm-load=1 ! 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.

Framerate measured

CPU Load

The CPU load was measured using tetrastats.

CPU measured


Performance


Home

NVidia TX1 EVM