Support configurable backoff intervals #163
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
cgillum
approved these changes
May 21, 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.
I was analyzing the cost of an app service with overall low volume (1-2 orchestrations per week), and right now the cost of the app service telemetry outweighs the cost of the basic app service.
Since the orchestrations I run are very tolerable of delays, I wanted to increase the maximum backoff values here to 5 minutes or more for a ~99% reduction in unnecessary telemetry.
As the orchestrations I run are just a hobby project, I'm not as familiar with the potential consequences of changing these values, especially with how they relate to each other. But I found the todo in the repo and figured I would start with the most basic implementation of passing it through on the settings object.