Skip to content

Conversation

@matthchr
Copy link
Member

  • this PR contains documentation
  • this PR contains tests
  • this PR contains YAML Samples

@matthchr
Copy link
Member Author

Opening this but want to do a bit more profiling before merging

# calls to Azure. Any single resource only blocks the control-loop for its resource-type for as long as it takes to issue
# an HTTP call to Azure, view the result, and make a decision. In most cases the time taken to perform these actions
# (and thus how long the loop is blocked and preventing other resources from being acted upon) is a few hundred
# milliseconds to at most a second or two. In a typical 60s period, many hundreds or even thousands of resources
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we need to scale back this comment? For some resources it's certainly true, but (as we've recently learned), not for all.

Suggested change
# milliseconds to at most a second or two. In a typical 60s period, many hundreds or even thousands of resources
# milliseconds to at most a second or two. In a typical 60s period, many hundreds of resources

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Development

Successfully merging this pull request may close these issues.

2 participants