Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • Icecast-Server Icecast-Server
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 103
    • Issues 103
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 6
    • Merge requests 6
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • External wiki
    • External wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Xiph.OrgXiph.Org
  • Icecast-ServerIcecast-Server
  • Issues
  • #2225
Closed
Open
Issue created Sep 16, 2015 by Marvin Scholz@ePiratOwner

Make listen backlog customizable

Excerpt from a mail we got on the list:

On 02/19/2015 03:07 PM, Stephan Leemburg wrote:

I am working for the NPO, the Dutch Public Broadcasting agency.

We do a lot of icecast streaming. We run at least 20 icecast server instances on our media streaming cluster. [...]

We ran into an issue that clients which where connecting to our streams seemed to be 'hanging' on the connection setup frequently. The client 'thinks' it is connected, but no data.

People suggested that it probably had to do with the poll() call. So, I looked into that.

I found that the issue was actually caused by the very low listen backlog (5). On our clusters, we typically set this to 8192. Yes it is high, but we do a lot of streaming and host very high volume websites.

Attached are the submitted patches for 2.4, 2.5 and 2.3.3

Assignee
Assign to
Time tracking