Measure element latency

[Nicolas Dufresne]

Le jeu. 13 juin 2019 11 h 10, clubberlang <taoming29 at gmail.com> a écrit :

> >  So best is if we get these tracer output hooks upstream, and then you
> can
> implement something on top, rather then inside of it.
>
> Is this what Michael suggested to hook a log handler? The reason I would
> like to emit those latency measurements is because I think writing to disks
> increases the CPU usage drastically. We want these measurements to be
> emitted as application metrics and in a cost-effective way -- not eat up
> too
> much CPU cycles for writing to file.
>

What I'm proposing is to add hooks so that application can gain access to
the GVariant containing the trace. Right now, we only support turning this
to string and logging through gstlog facility. Making metrics out of the
raw trace is left to application (like sysprof, gst-stats etc.)



>
>
> --
> Sent from: http://gstreamer-devel.966125.n4.nabble.com/
> _______________________________________________
> gstreamer-devel mailing list
> gstreamer-devel at lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/gstreamer-devel/attachments/20190613/275809ee/attachment.html>