LIV-1205: Transcoder overload protection. #181
Merged
Conversation
This file contains 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
- define config throttler.maxDataRate as max limit on transcoder usage. * measured in times x normal fps. e.g. if maxDataRate = 2 we expect no more than twice the original throughput. * By default maxDataRate is set to Infinity and no data rate limit is performed.
igorshevach
changed the title
…a rate * targetFrameRate)
david-winder-kaltura
approved these changes
Nov 13, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
add throttler.h,c
define config throttler.maxDataRate as max limit on transcoder usage.
define throttler.useStatsDataRate , bool (defaults: false) as a fallback suggesting use of stream times when estimating data rate. By default, given known fps (or packet per seconds, pps) throttler won't use dts'es as unreliable and calculate the rate from given target fps. NOTE: There are audio codecs like opus, where fps is not known and requires parsing packet header to determine actual number of audio samples, thus complicating the rate calculation.On the other hand, given aac is used most of the times the pps can be derived from a configuration data or assumed to be some max threshold value (e.g. 960 samples per frame)