214
edits
GstShark - Queue Level tracer: Difference between revisions
→Output
mNo edit summary |
(→Output) |
||
| Line 27: | Line 27: | ||
==Output== | ==Output== | ||
<font size=1> | <font size=1> | ||
<pre>0:00: | <pre> | ||
0:00: | 0:00:05.558210906 21193 0x5622294ee8f0 TRACE GST_TRACER :0:: queuelevel, queue=(string)queue0, size_bytes=(uint)9216000, max_size_bytes=(uint)10485760, size_buffers=(uint)20, max_size_buffers=(uint)20, size_time=(string)0:00:00.666666667, max_size_time=(string)0:00:01.000000000; | ||
0:00:05.591457397 21193 0x5622294ee850 TRACE GST_TRACER :0:: queuelevel, queue=(string)queue1, size_bytes=(uint)60587, max_size_bytes=(uint)10485760, size_buffers=(uint)11, max_size_buffers=(uint)200, size_time=(string)0:00:00.366666667, max_size_time=(string)0:00:00.400000000; | |||
</pre></font> | |||
Each line of the log includes a {{code|queue}} field identifying the element being measured, and three fields with the measurement of the queue level in bytes, buffers, and time. The results show the queue levels at the maximum established by the limits set on the pipeline. In practical applications, the queue level may be constrained by bottlenecks that do not provide the queue with enough data. | Each line of the log includes a {{code|queue}} field identifying the element being measured, and three fields with the measurement of the queue level in bytes, buffers, and time. The results show the queue levels at the maximum established by the limits set on the pipeline. In practical applications, the queue level may be constrained by bottlenecks that do not provide the queue with enough data. | ||
==Plot== | |||
[[File:Gstshark-examples-queuelevel.png|560px|center]] | |||
{{GstShark/Foot|previous=Bitrate tracer|next=Buffer tracer}} | {{GstShark/Foot|previous=Bitrate tracer|next=Buffer tracer}} | ||