[ci] Use %10 as default flagging threshold for x86_64 benchmarks #12915
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
antiagainst
added
the
infrastructure/benchmark
|
I think @pzread is also about to switch us over to c2-std-60 VMs, which means we get basically an entire VM to ourselves. This might be redundant with that. I'll let him make the call |
pzread
approved these changes
Apr 4, 2023
I'm fine to first loose the thresholds, we can re-adjust once the new data from c2-std-60 come in. |
NatashaKnk
pushed a commit
to NatashaKnk/iree
that referenced
this pull request
Jul 6, 2023
…e-org#12915) x86_64 benchmarks are not stable in general. Use a larger threshold to avoid being noisy.
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.
x86_64 benchmarks are not stable in general. Use a larger
threshold to avoid being noisy.