Bump goldentime values for mi250 sdxl benchmarks. #17860
Merged
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.
Seeing some variance causing CI failures with unrelated changes:
VAE Decode Benchmark Time: 295.0 ms (golden time 291.0 ms)
Prompt Encoder Benchmark Time: 17.2 ms (golden time 17.0 ms)
VAE Decode Benchmark Time: 295.0 ms (golden time 291.0 ms)
Prompt Encoder Benchmark Time: 17.1 ms (golden time 17.0 ms)
Aside: we might want to move the benchmarks to a
pkgci_benchmarks.yml
workflow instead of chaining them on to the end ofpkgci_regression_test.yml
.ci-exactly: build_packages,regression_test