rtmpdump updates for raspberry pi/raspbian

Neill Mitchell neill at nlkmitchell.com
Thu Jan 24 12:36:40 EST 2013


Hi Alex.

So were your downloads typically failing before the new version? If so, 
this goes some way to confirm that increasing rtmpdump's working buffer 
helps solve this problem with fast connections :)

Cheers
Neill.

On 24/01/13 17:00, get_iplayer-request at lists.infradead.org wrote:
>
> Here's a report using Jon's new debs for the Pi....
>
> I ran a couple of tests last night with a Pi and memory stick, but the
> results were a bit slow.
> The connection was a bit poor last night.
> This morning I rebooted the router and decide to use a NAS  for the
> downloaded file.
>
> Internet connection nominal 30 Mbaud
> (tested today at 0924: 28.97 Mbps)
>
> Pi was attached to NAS mounted via cifs through Gigabit ethernet.
>
> I downloaded Locomotion Episode 1 in HD
> start time 0900
>
> 20%  downloaded 0903
> 40%  downloaded 0906
> 71%  downloaded 0911
> 85%  downloaded 0912
> 100% downloaded 0915
>
> 1068546.537 kB total
>
> remuxing finished 0919
> file write finished 0922
>
> connection speed measured immediately afterwards: 28.97 Mbps
>
> CPU monitoring...
>
> During download:
> rtmpdump using 12-15% CPU
> flush-cifs-1 intermittently using up to 47% CPU
>
> While remuxing:
> ffmpeg 33%
> cifsd ~20%
> flush-cifs-1 ~ 44%
>
> Tagging/file write:
> flush-cifs-1 ~44% CPU
> cifsd - 27% CPU
> Atomic Parsley ~ 16% CPU
>
> And the most important test of all - watching the file works perfectly. :)
>
> Verdict EXCELLENT! Thanks Jon :) ~1 Gigabyte program downloaded and
> processed in 22 minutes.
> I don't think the Pi will do much better than that (although I could try
> it with an EXT4 USB HDD -
> that would be  quicker on the file writes)
>
>
>




More information about the get_iplayer mailing list