[benchmark] Disable some new Set tests with overlong runtime #24725
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.
PRs #23690 and #24156 have improved the performance coverage of
Set
type. The workloads in #24156 have been tune in with #21300 in mind. This means that some larger multipliers were selected assuming the presence of optimizations from #23100. This PR temporarily disables following test where it currently results in runtimes over 30 ms (these are guaranteed to include a context switch and are therefore more susceptible to be noisy and case false performance change):Set.isStrictSubset.Int100
Set.isStrictSubset.Seq.Empty.Int
Set.isStrictSuperset.Seq.Int.Empty