[1.16] Update perf test docs to point to the new source of truth #4961
+16
−150
Conversation
This file contains hidden or 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
Signed-off-by: Cassandra Coyle <[email protected]>
cicoyle
added
the
waiting-on-code-pr
cicoyle
removed
the
waiting-on-code-pr
Contributor
Author
|
code was merged. cc @marcduiker @msfussell this is good to go now |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Im adding automation to utilize our existing perf test suite in dapr/dapr & generate charts using code from our perf test suite runs. The idea is to have a folder per version with charts per API with READMEs explaining the tests and whatnot. This will get automated to create charts with every dapr release.
For now, I've moved the content from the actors and service invocation perf docs over to dapr/dapr, which will be the new source of truth for perf results/charts. This way too developers dont spin up one off tests, this is a repeatable pattern which requires no one off infra for testing as its already automated and repeatedly ran for us.
Depends on: PR for the charts for workflows and moving the actors and service invocation perf docs over.
Once I PR to master in dapr/dapr I can come back in and update the ref to the
release-1.16branch and instead point tomasterand PR here in the dapr/docs to the1.17branch