Implement a single-bucket design. #186
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
… handling of storage buckets. In future, we are going to use max 3 buckets per deployment (benchmarks, code, deployment). Warning: this has not been tested and evaluated on Azure, GCP, OpenWhisk and local - only AWS
…e benchmark 210.thumbnailer
…e-recognition inputs
…ric and implement storage function looking for existing deployments
…ing deployments and use them
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.
This PR resolves the issue #185. We have used too many buckets, creating issues on systems such as AWS with a hard limit of 100 buckets per account. In this design, a single SeBS deployment will only create up to three buckets: one for all benchmarks, one for code deployment, and one for experiments. On systems like Azure, we still use separate storage accounts for performance reasons.