Please provide complete information as applicable to your setup.
• Hardware Platform (Jetson / GPU) Jetson AGX Xavier • DeepStream Version Deepstream 6.0 • JetPack Version (valid for Jetson only) JetPack 4.6.1 • TensorRT Version 8
I am trying to install gst-shark and have it working on Jetson AGX Xavier. I was able to clone the repo, compile it and install it. I can also see the plugin for the tracer. However, when I run it with “interlatency”, or “cpuusage” etc., it does not give me any numbers. The only option that works is “latency”.
Can any of you help me with gst-shark on Jetson Xavier AGX?
Hi @raghavendra.ramya ,
As gst-shark is not developed or maintained by Nvidia, we are not able to support such plugin, maybe you have to go back to RidgeRun for help. Sorry for it.
Detailed descriptions and guides to each tracer are provided in the GstShark wiki page. I tested a fresh installation on a Xavier AGX with JetPack 4.6.1 and all the tracers were installed correctly. Here is the command:
Enable the tracers with the GST_DEBUG variable and then select the tracers wanted with GST_TRACERS. Here is a pipeline that uses the tracers you mentioned:
Thank you for responding. I tried the steps you suggested and gst-shark is working with latency, cpuusage and bitrate. But with interlatency, queuelevel, proctime I still get a segmentation fault. I am trying to use gst-shark with deepstream-app.
I tested these tracers with the DeepStream pipelines I use and they seem to be working correctly. Can you share the command and configs you are using to see if I can reproduce the issue? Are you using multiple tracers at the same time or just one at a time?
Thank you for your willingness to help. I am using just the Yolov3-tiny config file in the Deepstream folder. Which one did you use? I tried using single and multiple tracers, but I see the same issues.
@raghavendra.ramya I tested with a simple deepstream pipeline with the example config files. Can you test something similar on your side to see if you get the same error?
I am sorry for the delay, but I will get back to you regarding this, very soon.
I did not run this pipeline, I ran deepstream-app instead. I will run this exact pipeline and let you know what happens.
Thank you!