Add write benchmark to perf regression workflow #334
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
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.
Issue #, if available: n/a
Description of changes:
This PR adds write benchmarks to the performance regression workflow.
The mechanism is exactly the same as the read benchmarks, using the exact same datasets. This PR splits the deserialization results out into a new deserialization specific output, and adds the serialization results to a similar output. Both read and write benchmarks are compared separately. If either set of benchmarks has a >5% increase the workflow will fail. The output of both comparisons will be printed, and the output for each benchmark, as well as the comparisons are now uploaded as artifacts for review.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.