GSt Tracer Latency vs RidgeRun GSt Shark Inter-Latency

I have been trying to figure out the difference between these two tracing options so that I can better understand my DeepStream processing pipeline. I’m using Python (deepstream 6.2, cuda 11.8, ds python bindings etc.).

GStreamer seems to offer the following method to capture element latency

GST_DEBUG="GST_TRACER:7" "GST_TRACERS=latency(flags=element+pipeline)"

While Ridge Run GSt Shark (which seems popular) offers the following method


I was wondering if anyone knows the difference (if any) between these two tracers.

For GST_TRACER, please refer to Tracing (

For Gst Shark, please consult @michael_gruner

1 Like

Thanks, yes if Michael could provide some clarity on the differences that would be great!

You should use the GStreamer one (latency). Some years ago, the one in GstShark (interlatency) used to provide more information that latency, but they eventually caught up and absorbed these features.

1 Like

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.