AIESW-21287 add new qos parameter sleep_to_limit_fps #9540
+52
−4
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.
Problem solved by the commit
Add new qos parameter
sleep_to_limit_fpsto profile.json that can be used to simulate a model running at a fixed frame rateBug / issue (if any) fixed, which PR introduced the bug, how it was discovered
N/A
How problem was solved, alternative solutions (if any) and why they were rejected
Alternative solution is to use the existing
sleepparameter in theiterationnode inexecutions. This sleep duration is fixed, but since the sleep amount varies based on what else is running, it seems less brittle to automatically compute the sleep duration.Risks (if any) associated the changes in the commit
None unless this new parameter is used. Otherwise, we should consider this parameter experimental.
What has been tested and how, request additional testing if necessary
Ran full model tests both with and without this new parameter
Documentation impact (if any)
Potentially could document this new parameter