View previous topic :: View next topic |
Author |
Message |
JohnnyOh
Joined: 10 Feb 2009 Posts: 50 Location: Germany
|
Posted: Tue Mar 30, 2010 10:27 am Post subject: Icecast 100Mbit/s problem |
|
|
Hi together,
I am facing some weird behavior on icecast 2.3.2.
I have several Icecast servers streanming an amount of mp3-streams. Unfortunately the icecast servers are not able to deliver more than 100 Mbit/s.
Below you will find an extract of my icecast.xml:
Code: |
<?xml version="1.0" encoding="UTF-8"?>
<icecast>
<limits>
<clients>2500</clients>
<sources>200</sources>
<threadpool>250</threadpool>
<queue-size>524288</queue-size>
<client-timeout>30</client-timeout>
<header-timeout>15</header-timeout>
<source-timeout>10</source-timeout>
<!-- If enabled, this will provide a burst of data when a client
first connects, thereby significantly reducing the startup
time for listeners that do substantial buffering. However,
it also significantly increases latency between the source
client and listening client. For low-latency setups, you
might want to disable this. -->
<burst-on-connect>1</burst-on-connect>
<!-- same as burst-on-connect, but this allows for being more
specific on how much to burst. Most people won't need to
change from the default 64k. Applies to all mountpoints -->
<burst-size>65535</burst-size>
</limits>
<authentication>
<!-- Sources log in with username 'source' -->
<source-password>hackme</source-password>
<!-- Relays log in username 'relay' -->
<relay-password>hackme</relay-password>
<!-- Admin logs in with the username given below -->
<admin-user>admin</admin-user>
<admin-password>hackme</admin-password>
</authentication>
<!-- set the mountpoint for a shoutcast source to use, the default if not
specified is /stream but you can change it here if an alternative is
wanted or an extension is required
<shoutcast-mount>/live.nsv</shoutcast-mount>
-->
<!-- Uncomment this if you want directory listings -->
<!--
<directory>
<yp-url-timeout>15</yp-url-timeout>
<yp-url>http://dir.xiph.org/cgi-bin/yp-cgi</yp-url>
</directory>
-->
<!-- This is the hostname other people will use to connect to your server.
It affects mainly the urls generated by Icecast for playlists and yp
listings. -->
<hostname>localhost</hostname>
<!-- You may have multiple <listener> elements -->
<listen-socket>
<port>80</port>
<!-- <bind-address>127.0.0.1</bind-address> -->
<!-- <shoutcast-mount>/stream</shoutcast-mount> -->
</listen-socket>
<!--
<listen-socket>
<port>8001</port>
</listen-socket>
-->
<!--<master-server>127.0.0.1</master-server>-->
<!--<master-server-port>8001</master-server-port>-->
<!--<master-update-interval>120</master-update-interval>-->
<!--<master-password>hackme</master-password>-->
<!-- setting this makes all relays on-demand unless overridden, this is
useful for master relays which do not have <relay> definitions here.
The default is 0 -->
<!--<relays-on-demand>1</relays-on-demand>-->
<!--
<relay>
<server>127.0.0.1</server>
<port>8001</port>
<mount>/example.ogg</mount>
<local-mount>/different.ogg</local-mount>
<on-demand>0</on-demand>
<relay-shoutcast-metadata>0</relay-shoutcast-metadata>
</relay>
-->
|
I tested the network connection. The servers are able to deliver 1 GBit/s. It seems that Icecast is the limiting factor. There are no limitation defined for the relays or connections.
Could you please tell me what I have to configure that the servers are able to deliver 1 GBit/s or more?
Kind regards
Johnny |
|
Back to top |
|
|
karlH Code Warrior
Joined: 13 Jun 2005 Posts: 5476 Location: UK
|
Posted: Tue Mar 30, 2010 2:01 pm Post subject: |
|
|
There's no bandwidth limiting within 2.3.2. What can you tell us about the test setup, home many streams, how many clients, is this on win32? is the CPU being max'd out etc
karl. |
|
Back to top |
|
|
JohnnyOh
Joined: 10 Feb 2009 Posts: 50 Location: Germany
|
Posted: Wed Mar 31, 2010 8:26 am Post subject: |
|
|
Hi Karl,
thank you for your reply.
I am using icecast on debian based systems (some etch, some lenny).
This is the output of top on one of the systems:
Code: |
top - 11:34:52 up 7 days, 14:50, 1 user, load average: 0.17, 0.06, 0.02
Tasks: 73 total, 1 running, 72 sleeping, 0 stopped, 0 zombie
Cpu(s): 0.3%us, 0.9%sy, 0.0%ni, 97.3%id, 0.0%wa, 0.3%hi, 1.1%si, 0.0%st
Mem: 3632160k total, 2076796k used, 1555364k free, 171684k buffers
Swap: 8691156k total, 0k used, 8691156k free, 1709476k cached
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
1610 nobody 15 0 77728 20m 2052 S 5 0.6 407:27.50 icecast
|
there are no other processes running which could affect a high network or cpu load. |
|
Back to top |
|
|
als
Joined: 14 Oct 2008 Posts: 18
|
Posted: Fri May 28, 2010 3:23 pm Post subject: |
|
|
We have >1 year icecast running at ~ 150 Mbit on vps (xen) with Debian 4.0 |
|
Back to top |
|
|
m3gab0y
Joined: 15 Aug 2009 Posts: 47 Location: London, UK
|
Posted: Tue Jun 01, 2010 2:04 pm Post subject: |
|
|
This is really strange. I run a few huge icecast servers on private peering network with 10+k of listeners at peak times and no problems so far. |
|
Back to top |
|
|
gimlioak
Joined: 21 Apr 2010 Posts: 13
|
Posted: Mon Jun 14, 2010 9:34 am Post subject: |
|
|
Hello,
No prob here using icecast on 1Gbps connection. It's running smooth. I'm using Debian 5 and Ubuntu 9.04.
HTH
Jef |
|
Back to top |
|
|
JohnnyOh
Joined: 10 Feb 2009 Posts: 50 Location: Germany
|
Posted: Wed Jul 14, 2010 1:41 pm Post subject: |
|
|
Now everything works fine. I did a reinstall and everything worked fine. I have no idea what the reason for this problem was. |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
Powered by phpBB © 2001, 2002 phpBB Group subRebel style by ktauber
|