Skip to content

feat: Set jicofo max-bridge-participants-per-interval to 30 - #942

Merged
bgrozev merged 1 commit into
jitsi:mainfrom
bgrozev:jicofo-max-bridge-participants-per-interval
Aug 6, 2026
Merged

feat: Set jicofo max-bridge-participants-per-interval to 30#942
bgrozev merged 1 commit into
jitsi:mainfrom
bgrozev:jicofo-max-bridge-participants-per-interval

Conversation

@bgrozev

@bgrozev bgrozev commented Aug 6, 2026

Copy link
Copy Markdown
Member

Enables the new jicofo per-conference bridge join-rate limit everywhere, via two new role variables:

  • jicofo_max_bridge_participants_per_interval, default 30 (the feature is on by default, use -1 to disable)
  • jicofo_max_bridge_participants_interval, default 1 minute

They render as jicofo.bridge.max-bridge-participants-per-interval / max-bridge-participants-interval in jicofo.conf.

A bridge reports its stress level only every 5-10 seconds, so during a burst of joins the reported stress is stale and jicofo keeps assigning to the same bridge long after it is full. Seen in production: a conference added 92 endpoints in 31 seconds, 58 of them on one bridge which reached a stress of 1.1, while 9-11 bridges in the same pool stayed below 0.05. The limit caps how many endpoints a single conference may add to a single bridge per interval, which spreads the burst. A conference which grows slowly, and many small conferences sharing a bridge, are unaffected.

Requires jitsi/jicofo#1298. Older jicofo versions ignore the unknown keys.

@bgrozev
bgrozev merged commit cbcd114 into jitsi:main Aug 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants