After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 722095 - RTP over UDP uses queue and appsink
RTP over UDP uses queue and appsink
Status: RESOLVED DUPLICATE of bug 758179
Product: GStreamer
Classification: Platform
Component: gst-rtsp-server
git master
Other Linux
: Normal enhancement
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2014-01-13 11:19 UTC by Jonas Holmberg
Modified: 2016-08-25 14:09 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
drop queue buffers (3.77 KB, patch)
2014-01-13 11:23 UTC, Jonas Holmberg 		needs-work Details | Review

Description Jonas Holmberg 2014-01-13 11:19:32 UTC 
When streaming over UDP there are elements in the pipeline that are not needed. Some of them are queues which start threads. This causes performance problems on embedded systems (tested on mips and arm).
Comment 1 Jonas Holmberg 2014-01-13 11:23:34 UTC 
Created attachment 266147 [details] [review]
drop queue buffers

This patch was used for comparison when testing. It increases performance by dropping all buffers at the sinkpad of the queues. It is just for testing. The right solution is probably to build the pipeline after RTSP SETUP instead, when the transport protocols are known.
Comment 2 Wim Taymans 2014-02-04 14:06:35 UTC 
Needs some more work. For now you can remove TCP from the transport to remove the queues.
Comment 3 Jonas Holmberg 2014-02-07 11:32:40 UTC 
How can we remove TCP from protocols? The pipeline is created (with queue and appsink) before RTSP SETUP is received. I.e. before we know what transport protocol to use.
Comment 4 Sebastian Dröge (slomo) 2015-04-28 12:12:41 UTC 
You can set the allowed protocols on the media
Comment 5 Jonas Holmberg 2016-08-25 14:09:55 UTC 

*** This bug has been marked as a duplicate of bug 758179 ***