Add a key management simulator for data protection #55348
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
It's not properly a sample, since it requires IVT, but it's much easier to read and use as a standalone app than as a test. (It would also make a poor test, since perfect performance is not expected and thus there's no way to define success.) Simulates running an app with a given number of instances for a given number of days and computes a score (lower is better) indicating how likely missing key errors were during that simulated time period. Also tracks calls to the storage and encryption backends so we can see whether e.g. retries have a significant perf impact. In the future, it would be nice if instances started and stopped over the course of the run, rather than all living for the entire duration.
BrennanConroy
approved these changes
May 1, 2024
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.
It's not properly a sample, since it requires IVT, but it's much easier to read and use as a standalone app than as a test. (It would also make a poor test, since perfect performance is not expected and thus there's no way to define success.)
Simulates running an app with a given number of instances for a given number of days and computes a score (lower is better) indicating how likely missing key errors were during that simulated time period. Also tracks calls to the storage and encryption backends so we can see whether e.g. retries have a significant perf impact.
In the future, it would be nice if instances started and stopped over the course of the run, rather than all living for the entire duration.