Problems with GstShark - RidgeRun

Wed Jun 5 22:09:39 UTC 2019

Hi Nicolas,

  Thanks for jumping in.  Our goal with GstShark is to provide a tool to developers so they can identify bottlenecks in the pipelines in an easy, visual way. The first step towards that was to add CTF support to the project. Next we wanted to provide a nice visualisation tool  to consume this CTF and plot the data, even en real time. We never quite got to the later (yet).

  It would be great if we could use your tracers as well, and eventually merge ours into mainline. That would leave GstShark as an independent front-end, and RidgeRun would focus on developing hardware specific tracers. A good starting point for the transition is to add CTF support to your tracers.  We can clean up the CTF support and prepare a merge request into GStreamer.

Would that be something someone on your team could review and work with us to merge in mainline? 

Regards,
Michael

PD:

> For cpuusage, that sounds very similar to upstream rusage tracer. Could be nice if someone tells me
> the difference.

The CPU tracers is simply that, prints the CPU usage every N seconds. To do so it parses /proc/stat instead of using getrusage() as you do. There is no reason to keep it if rusage is upstream, it’s there because we weren’t aware of yours back then on 1.7 when tracing first started. We need the CTF output though.

> On Jun 4, 2019, at 8:43 PM, Nicolas Dufresne <nicolas at ndufresne.ca> wrote:
> 
> Le mardi 04 juin 2019 à 21:29 -0400, John Hanks a écrit :
>> This seems to work with the command line example but when I try it from 
>> my C-program using these lines in the code:
>> 
>> setenv("GST_TRACERS","latency(flags=pipeline+elemen+reported)",TRUE);
>>     setenv("GST_DEBUG","GST_TRACER:7" ,TRUE);
>> 
>> I get no 'trace' output.  Any idea what am I doing wrong?
> 
> Do you properly set the env before calling gst_init() (or any variant
> of this) ?
> 
>> 
>> John
>> 
>> On 5/31/19 08:11, Nicolas Dufresne wrote:
>>> Le jeudi 30 mai 2019 à 22:30 -0400, John Hanks a écrit :
>>>> In case others are having similar problems.  gst-shark is not providing the output it should.
>>>> Has anyone else had similar issues?
>>> The latency and interlatency tracers in GstShark are no longer useful
>>> in my opinion. Julian and I (Collabora) have fixed many issues and came
>>> up with a completely upstream solution for this.
>>> 
>>> Since 1.16, you can now use the upstream latency tracer to get three
>>> type of information:
>>> 
>>>   - Complete pipeline latency
>>>   - Per element latency (not the cumulative like interlatency did)
>>>   - Per element reported latency
>>> 
>>> To enable all of these:
>>> 
>>> GST_TRACERS="latency(flags=pipeline+elemen+reported)" GST_DEBUG=GST_TRACER:7 ./...
>>> 
>>> 
>>> The initial issue we had with the RidgeRun implementation was a bug
>>> inherited from the original upstream tracer. The time spent in the the
>>> wait function of the sink was included. We also found that the
>>> cumulative latency wasn't so nice to debug the reported latency. The
>>> reported latency tracing is completely new. That being said, thanks to
>>> RidgeRun for the proof of concept.
>>> 
>>> Nicolas
>>> 
>>>> John
>>>> 
>>>> 
>>>> -------- Forwarded Message --------
>>>> Subject:	Vsicorp: Problems with GstShark - RidgeRun
>>>> Date:	Wed, 29 May 2019 14:50:45 +0000 (GMT)
>>>> From:	Carlos Rodriguez <carlos.rodriguez at ridgerun.com>
>>>> To:	John Hanks <jhanks at vsicorp.com>, support <support at ridgerun.com>
>>>> CC:	Miguel Angel Taylor López <miguel.taylor at ridgerun.com>
>>>> 
>>>> 
>>>> Hi John,
>>>> 
>>>> Thanks for your interest in our products and services. RidgeRun is a company with over a decade of embedded Linux experience supporting NVIDIA, Xilinx, Freescale/NXP, and Texas Instruments SoC. RidgeRun focuses on embedded Linux and GStreamer. Many, but not all, of our customers are doing some sort of audio / video streaming ( https://shop.ridgerun.com/collections/all).
>>>> 
>>>> Miguel (CC'ed) will help you with this GstShark problem. He will provide support shortly.
>>>> 
>>>> Regards,
>>>> - Carlos R.
>>>> ----------------------------------------------------------------------------------------------
>>>> Ticket Name: Problems with GSTShark
>>>> 
>>>> Ticket Description:
>>>> 
>>>> I've been working with gstreamer for about a year and wanted to use your tools to profile my working pipelines (actually, programs) so I could debug future problems. I followed the instructions to 'git', make and install the code but I must have done something wrong.  The only time it seems to do anything is when I set GST_TRACERS=latency.  It then displays the latency in the running window like this:
>>>> 
>>>> 0:00:01.739608128 4356 0xbb04a0 TRACE GST_TRACER :0:: latency, src=(string)videotestsrc0_src, sink=(string)fakesink0_sink, time=(guint64)1558941909, ts=(guint64)1739572905;
>>>> 0:00:01.773075049 4356 0xbb04a0 TRACE GST_TRACER :0:: latency, src=(string)videotestsrc0_src, sink=(string)fakesink0_sink, time=(guint64)1588456647, ts=(guint64)1773053449;
>>>> 0:00:01.806234476 4356 0xbb04a0 TRACE GST_TRACER :0:: latency, src=(string)videotestsrc0_src, sink=(string)fakesink0_sink, time=(guint64)1617668782, ts=(guint64)1806211230;
>>>> 
>>>> This output is odd because what I read says the it should create a new subdirectory and dump the information in a file.  Even when I set that directory (GST_SHARK_LOCATION), it still dumps latency o the screen and and never creates a file.
>>>> 
>>>> If I try any of the other tracers (cpuusage,framerate, etc) it just hangs after starting the pipeline - and that is your example pipelines from the wiki.
>>>> 
>>>> I'm guessing I must have done something wrong with the installation but cannot figure out what.
>>>> 
>>>> I'm running Ubuntu 16.04.6.
>>>> 
>>>> Any ideas what I am doing wrong?
>>>> 
>>>> John
>>>> 
>>>> 
>>>> 
>>>> Tuesday, May 28, 2019 8:05:08 PM CST, John Hanks <jhanks at vsicorp.com>:
>>>> _______________________________________________
>>>> gstreamer-devel mailing list
>>>> gstreamer-devel at lists.freedesktop.org
>>>> https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel
>>> _______________________________________________
>>> gstreamer-devel mailing list
>>> gstreamer-devel at lists.freedesktop.org
>>> https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel
>> _______________________________________________
>> gstreamer-devel mailing list
>> gstreamer-devel at lists.freedesktop.org
>> https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel
> 
> _______________________________________________
> gstreamer-devel mailing list
> gstreamer-devel at lists.freedesktop.org <mailto:gstreamer-devel at lists.freedesktop.org>
> https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel <https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/gstreamer-devel/attachments/20190605/190af562/attachment-0001.html>