Add load_distribution strategy (consolidate | spread)#1248
Open
chalapathi444 wants to merge 1 commit into
Open
Add load_distribution strategy (consolidate | spread)#1248chalapathi444 wants to merge 1 commit into
chalapathi444 wants to merge 1 commit into
Conversation
Adds a `load_distribution` service config that controls how the affinity scorer routes egress jobs across server instances: - "consolidate" (default, unchanged behavior): packs jobs onto already busy servers, keeping idle servers free for heavier egress types (room composite, web). - "spread": routes each job to the server with the most available CPU, distributing load evenly. Recommended for track-only deployments. The spread strategy uses a new Monitor.AvailableCPURatio() as the affinity score, so the server with the most headroom wins each selection round. Defaults to "consolidate" when unset.
|
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds a
load_distributionservice config that controls howStartEgressAffinityroutes jobs across server instances.Why
The current affinity scorer always consolidates: idle servers return a lower score so jobs pack onto already-busy instances, keeping idle servers free for heavier egress types (room composite, web). That is ideal for mixed deployments, but for track-only fleets it concentrates load and leaves headroom stranded.
How
consolidate(default): unchanged behavior — packs jobs onto busy servers.spread: returns a newMonitor.AvailableCPURatio()as the affinity score, so the server with the most available CPU wins each selection round and load is distributed evenly.AvailableCPURatio()reuses the existinggetCPUUsageLocked()accounting and is clamped to[0, 1]. Defaults toconsolidatewhen unset, so existing deployments are unaffected.Notes
gofmtclean. Verified compilation and interface satisfaction locally; I couldn't run the GStreamer-dependent integration suite in my environment, so a CI run is appreciated.