[Bug 694405] souphttpsrc: improve performance / efficiency

GStreamer (bugzilla.gnome.org) bugzilla at gnome.org
Sat Jun 8 19:19:23 PDT 2013


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

zhangyanping <zhangyanping210> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |NOTABUG

--- Comment #9 from zhangyanping <zhangyanping210 at yahoo.com.cn> 2013-06-09 02:11:43 UTC ---
Hello all,

        I tested this problem again. My gstreamer version is 1.0.5.

        I found that the argment "blocksize" is very important for this
problem.

        I use this command to test:

gst-launch-1.0 souphttpsrc location=http://10.209.162.77/yt_aware.mp4
blocksize=4096 ! fakesink

When 
blocksize = 4096, average bitrate is 8Mbps, CPU nearly 100%
blocksize = 8192, average bitrate is 27M, CPU nearly 100%
blocksize = 16384, average bitrate is 36M, CPU nearly 100%
blocksize = 32768 , average bitrate is 44M, CPU nearly 100%
blocksize = 65536 , average bitrate is 47M, CPU nearly 100%
blocksize = 131072, average bitrate is 47M, CPU nearly 100%

So I changed the default blocksize for souphttpsrc to 64K. I think there are
some looping cost the time. For 64Kb data, if blocksize is 64Kb, just one loop
can push it to sink. If blocksize is 4Kb, there will be 16 times loop.

The souphttpsrc average bitrate(47M) is less than curl(54M). There may be some
efficence loss during gstreamer and libsoup. But I don't care this. 47M is
enough.
So I think this issue can be closed.

Thanks.

-- 
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.


More information about the gstreamer-bugs mailing list