search for: chunklen

Hi all, we got a new test system here and I just also tested btrfs raid6 on that. Write performance is slightly lower than hw-raid (LSI megasas) and md-raid6, but it probably would be much better than any of these two, if it wouldn''t read all the during the writes. Is this a known issue? This is with linux-3.9.2. Thanks, Bernd -- To unsubscribe from this list: send the line

...quot;Client kicked becouse of to many error: client did not receive data fast enough". Even if my Upstream-Bandwitd via Cable-Modem isn't soo big, but I think about 200 kbits/s should be enough for some (but at least one) Listener for a 32kbps-Stream. I did recompile Icecast with a doubled chunklen. Then I don't get this Error anymore but the client mostly gets out of synch after some reconnects. This problem dont't occour in icecast's static mp3-file streaming of the by darkice dumped files. Does anybody have ideas what my problem could be? Does icecast in live streaming need at...

...distribution), you will likely hear "looping" problems, so make sure to get it. Some things that seemed to improve network performance and help crappy players like RealAudio not rebuffer: in src/icetypes.h, change the default values (8192 and 64) to these: #define BUFSIZE 16384 #define CHUNKLEN 128 And in /etc/rc.local (or another script run by root), add this: # Max out some network parameters for potential throughput improvement /sbin/sysctl -w kern.ipc.maxsockbuf=1048576 /sbin/sysctl -w net.inet.tcp.sendspace=32768 /sbin/sysctl -w net.inet.tcp.recvspace=32768 These made an obvious di...

Hello everyone, I am very tempted to try and use icecast as the weapon of choice to realize a live audio stream for the radio station I work for. Now, the last time I tried the FreeBSD port of Icecast, it immediately consumed something like 95% CPU time, even without any client connected. I think someone else reported that problem, but I somehow lost track of the issue - has this been

Hi Karl, Thanks for your help, About the "Connection:" header, you are right, it's: "Connection: close" and NOT "Connection: keep-alive". The protocol when the SERVER sends the data is http 1.0. It's http 1.1 when the browser requests the data. I don't understand the "Content-Length: 54000000" header either. Also I noticed the flash player on