NVIDIA Jetson: Difference between revisions

From RidgeRun Developer Wiki
No edit summary
 
mNo edit summary
 
Line 1: Line 1:
{{GstRtspSink/Head|previous=Performance|next=Client Applications|keywords=}}
{{GstRtspSink/Head|previous=Performance|next=Client Applications}}


This wiki presents some performance measurements of a typical GstRtspSink pipeline on the NVidia TX2 running for 2:40 hours.
This wiki presents some performance measurements of a typical GstRtspSink pipeline on the NVIDIA TX2 running for 2:40 hours.
<br>
<br>
{{NVIDIA Pref Partner logo and RR Contact}}
<br>
<br>
<table>
<td>
<tr>
<td><div class="clear; float:right">__TOC__</div></td>
<td valign=top>
{{GStreamer debug}}
{{GStreamer debug}}
</td>
</td>
</table>
<br>
<br>
The pipeline ran without clients, after 1h one client is connected to the stream.  
The pipeline ran without clients, after 1h one client is connected to the stream.  

Latest revision as of 13:53, 18 December 2024


Previous: Performance Index Next: Client Applications




This wiki presents some performance measurements of a typical GstRtspSink pipeline on the NVIDIA TX2 running for 2:40 hours.






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



The pipeline ran without clients, after 1h one client is connected to the stream.

GstRtspSink Pipeline

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

PORT=5000
MAPPING=/stream1
gst-launch-1.0 videotestsrc is-live=true ! video/x-raw, width=1920, height=1080, framerate=60/1 ! queue ! nvvidconv ! nvv4l2h264enc insert-sps-pps=true idrinterval=30 ! perf print-cpu-load=true ! video/x-h264, mapping=${MAPPING} ! rtspsink service=${PORT}

NVIDIA TX2

Framerate

The frame rate was measured using the perf element.

Framerate measured

CPU Load

The CPU load was measured using perf element.

CPU measured

RAM Usage

The ram usage was measured using massif.

Ram measured

Jetson Nano

Framerate, bitrate, and CPU load

The frame rate was measured using the perf element.

timestamp: 0:47:20.043277758; bps: 3833104,000; mean_bps: 3833104,000; fps: 52,062; mean_fps: 52,403; cpu: 32; 
timestamp: 0:47:21.061018592; bps: 3624256,000; mean_bps: 3728680,000; fps: 52,076; mean_fps: 52,294; cpu: 32; 
timestamp: 0:47:22.062444493; bps: 3366536,000; mean_bps: 3607965,333; fps: 51,926; mean_fps: 52,202; cpu: 33; 
timestamp: 0:47:23.077551507; bps: 3416872,000; mean_bps: 3560192,000; fps: 52,211; mean_fps: 52,204; cpu: 32; 
timestamp: 0:47:24.095062536; bps: 3607152,000; mean_bps: 3569584,000; fps: 52,088; mean_fps: 52,185; cpu: 32; 
timestamp: 0:47:25.112565228; bps: 3544072,000; mean_bps: 3565332,000; fps: 52,088; mean_fps: 52,171; cpu: 32; 
timestamp: 0:47:26.129608896; bps: 3326272,000; mean_bps: 3531180,571; fps: 52,112; mean_fps: 52,163; cpu: 32; 
timestamp: 0:47:27.147234190; bps: 3505936,000; mean_bps: 3528025,000; fps: 52,082; mean_fps: 52,154; cpu: 32; 
timestamp: 0:47:28.164591559; bps: 3526680,000; mean_bps: 3527875,556; fps: 52,096; mean_fps: 52,149; cpu: 32; 
timestamp: 0:47:29.182429770; bps: 3428696,000; mean_bps: 3517957,600; fps: 52,071; mean_fps: 52,141; cpu: 32;

Jetson Xavier

Framerate

The frame rate was measured using the perf element.


CPU Load

The CPU load was measured using perf element.


RAM Usage

The ram usage was measured using massif.



Previous: Performance Index Next: Client Applications