feat: stagger startup of containers on Azure #3371
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
Seeing some cases where starting up large (80+ workers) load tests on ACI seems to exceed some underlying Azure Blob Storage limits with multiple containers all accessing the same blob container concurrently. With this change Artillery will pause for up to 10 seconds after launching every batch of 10 workers.
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.
Description
Seeing some cases where starting up large (80+ workers) load tests on ACI seems to exceed some underlying Azure Blob Storage limits with multiple containers all accessing the same blob container concurrently.
With this change Artillery will pause for up to 10 seconds after launching every batch of 10 workers.
Pre-merge checklist
This is for use by the Artillery team. Please leave this in if you're contributing to Artillery.