[Red5] About the VOD playback performance check-in
spam at electroteque.org
Fri Feb 15 05:27:18 PST 2008
Ok i changed the loadtester app to include a buffertime of 10 seconds.
Our players are set to 8 by default.
top - 00:25:50 up 4:20, 2 users, load average: 0.47, 0.34, 0.16
Tasks: 119 total, 1 running, 118 sleeping, 0 stopped, 0 zombie
Cpu0 : 1.0%us, 0.7%sy, 0.0%ni, 98.3%id, 0.0%wa, 0.0%hi,
Cpu1 : 1.3%us, 1.0%sy, 0.0%ni, 95.0%id, 0.0%wa, 1.3%hi,
Mem: 1029420k total, 898280k used, 131140k free, 348k buffers
Swap: 1959888k total, 0k used, 1959888k free, 605128k cached
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
8775 root 17 0 429m 104m 10m S 6 10.4 0:29.67 java
It went between 1-30% I saw 5 and 6% alot.
I think you nailed it. I will test on proper traffic tommorow or monday.
On 15/02/2008, at 11:50 PM, Steven Gong wrote:
> Hi all,
> I just checked in the update that might alleviate the VOD playback
> performance issue on trunk r2649. This is a conservative solution
> though as I don't plan to change a lot to the code base before the
> release. There are several possible solutions to enhance the
> performance which need more code changes and I will put off the
> check-in after 0.7 release.
> This check-in changes a little of the behavior server controls the
> VOD client buffer duration. I found the more client buffer duration
> the clients set, the server can provide more capacities for VOD
> streaming. This is because the server needs to track the client play
> buffer to make sure it neither overflow nor underflow. If the play
> buffer is small, the server needs a smaller interval for the check
> which needs more processing. The original implementation of this
> check is always use the 10ms interval and now it is enhanced to use
> the interval per the client buffer duration setting which is
> getClientBufferDuration()/10. And the minimal client buffer duration
> that takes effect could be set as a property of
> PlaylistSubscriberStream. The default value is 1s which means the
> check interval is 100ms.
> To get a good server capacity, it is recommended to set a big client
> buffer duration on the client side. Normally 5s or 10s is a good
> value. Or you can set the minimal client buffer duration on the
> server to a big value globally.
> As we are about to release 0.7 soon, I appreciate much your help for
> testing this check-in (great if you can use a dual-buffer algorithm
> client against the server) and report any issues you find. Thanks!
> Best Regards
> Steven Gong
> InfraRed5 Red5 Consultant: http://www.infrared5.com, steven at infrared5.com
> Red5 Developer: http://osflash.org/red5, http://jira.red5.org/confluence/display/
> Javaflash Project Founder and Maintainer: http://osflash.org/javaflash
> Modesty is an overrated quality in men of no great accomplishment.
> -- Ricky Jay _______________________________________________
> Red5 mailing list
> Red5 at osflash.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Red5