[Bug 740149] rtspsrc cpu optimization

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=740149
  GStreamer | gst-plugins-good | 1.4.4

Nicolas Dufresne (stormer) <nicolas.dufresne> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |nicolas.dufresne at collabora.
                   |                            |co.uk

--- Comment #7 from Nicolas Dufresne (stormer) <nicolas.dufresne at collabora.co.uk> 2014-11-19 17:36:26 UTC ---
For profiling, I would like to suggest "per top -g". It's live and intuitive,
but it's a matter of perception. You can also do "perf record <command>", and 
then use "perf report perf.data" to analyze afterward.

You could experiment with the rtspsrc properties. Few that may make a
difference are:

"udp-buffer-size" This will play on the amount of data the socket can
accumulate. Not sure of the impact on CPU, but clearly will help compensate for
high CPU load.

"do-rtcp" / "do-rtsp-keep-alive" Not doing RTCP may of course help reducing CPU
(hopefully this isn't why libav RTSP stack is faster)

"rtp-blocksize" The smaller the buffers, that higher the CPU, I think this is
just a suggestion toward the server, don't put to much hope there

"buffer-mode" Only make sense if profiling points to buffering code

Anything that make sense base on what exact part is using CPU. Of course you
need debug symbols of everything involved (kernel vmlinuz is highly
recommended, since CPU utilization can be due to hammering the socket API).

Also, if you attached profiling data here, you are more likely to get helped in
this investigation of potential performance bottleneck. That's what we mean by
NEEDINFO. If you prefer to use another stack, that would be your choice, please
close that bug in that case.

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.