GODRIVER-3102: Post perf comparison #2124
Closed
+288
−0
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
API Change ReportNo changes found! |
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.
GODRIVER-3102
Summary
internal/cmd/perfnotif/main.gocan be run locally to get a Markdown output of performance benchmarks marked with the Go Driver perf (h-score) performance context.To test, please run the following commands in
mongo-go-driver:To get the full commit name, you can run
git rev-parse <short>on the short commit name you find in GitHub.To test with a commit with known marked change points, use
50cf0c20d228975074c0010bfb688917e25934a4as the commit number.Background & Motivation
View benchmarks on current commit that are marked with the "Go Driver perf (h-score)" triage context, run locally.