I set up 3 streams and add FPS count before and after the nvstreammux using the src buffer callbacks or the gst-perf element. I expect to have 30 FPS (total 90) on each input stream (before inference) and some slow down after the inference (in my case, total about 70). But what I see is that FPS is the same on both postdecode_queue_0 and the queue after demux and it is about 70. That’s why I think there is some kind of drop somewhere, but I can’t understand where exactly.
Also, if I add a leaky queue before the nvstreammux, I will have total FPS 90 (as produces by the camera)
gst-launch-1.0 \
nvstreammux name=mux batch-size=3 width=2048 height=1536 live-source=1 \
nvstreamdemux name=demux \
rtspsrc location=rtsp://192.168.100.109:554/cam0_0 ! rtph265depay ! h265parse ! perf name=preinfer_0 ! queue leaky=1 flush-on-eos=true ! nvv4l2decoder ! nvvideoconvert ! mux.sink_0 \
rtspsrc location=rtsp://192.168.100.109:554/cam0_0 ! rtph265depay ! h265parse ! perf name=preinfer_1 ! queue leaky=1 flush-on-eos=true ! nvv4l2decoder ! nvvideoconvert ! mux.sink_1 \
rtspsrc location=rtsp://192.168.100.109:554/cam0_0 ! rtph265depay ! h265parse ! perf name=preinfer_2 ! queue leaky=1 flush-on-eos=true ! nvv4l2decoder ! nvvideoconvert ! mux.sink_2 \
mux.src ! nvvideoconvert ! nvinfer config-file-path=..yolo/yolo.txt name=nvinfer ! demux.sink \
demux.src_0 ! queue ! perf name=postinfer_0 ! fakesink sync=1 \
demux.src_1 ! queue ! perf name=postinfer_1 ! fakesink sync=1 \
demux.src_2 ! queue ! perf name=postinfer_2 ! fakesink sync=1
The output will be like
perf: preinfer_0; ... fps: 29.981 ...
perf: postinfer_0; ... fps: 14.390 ...
But here the leaky queue is the one who explicitely drops the frames