Use a consistent scale factor and resolution in stress tests#10474
Merged
alice-i-cecile merged 1 commit intobevyengine:mainfrom Nov 9, 2023
Merged
Use a consistent scale factor and resolution in stress tests#10474alice-i-cecile merged 1 commit intobevyengine:mainfrom
alice-i-cecile merged 1 commit intobevyengine:mainfrom
Conversation
alice-i-cecile
added
A-Rendering
alice-i-cecile
approved these changes
Nov 9, 2023
Member
Yes, but in a follow-up PR :)
If we're able to deduplicate more code than just that into a common helper file, sure. |
Contributor
|
Yeah, agree with this. |
ickshonpe
approved these changes
Nov 9, 2023
JMS55
approved these changes
Nov 9, 2023
alice-i-cecile
added
the
S-Ready-For-Final-Review
rdrpenguin04
pushed a commit
to rdrpenguin04/bevy
that referenced
this pull request
Jan 9, 2024
…ine#10474) # Objective Related to bevyengine#10472. Not having a hardcoded scale factor makes comparing results from these stress tests difficult. Contributors using high dpi screens may be rendering 4x as many pixels as others (or more). Stress tests may have different behavior when moved from one monitor in a dual setup to another. At very high resolutions, different parts of the engine / hardware are being stressed. 1080p is also a far more common resolution for gaming. ## Solution Use a consistent 1080p with `scale_factor_override: 1.0` everywhere. In bevyengine#9903, this sort of change was added specifically to `bevymark` and `many_cubes` but it makes sense to do it everywhere. ## Discussion - Maybe we should have a command line option, environment variable, or `CI_TESTING_CONFIG` option for 1080p / 1440p / 4k. - Will these look odd (small text?) when screenshotted and shown in the example showcase? The aspect ratio is the same, but they will be downscaled from 1080p instead of ~720p. - Maybe there are other window properties that should be consistent across stress tests. e.g. `resizable: false`. - Should we add a `stress_test_window(title)` helper or something? - Bevymark (pre-10472) was intentionally 800x600 to match "bunnymark", I believe. I don't personally think this is very important.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Objective
Related to #10472.
Not having a hardcoded scale factor makes comparing results from these stress tests difficult.
Contributors using high dpi screens may be rendering 4x as many pixels as others (or more). Stress tests may have different behavior when moved from one monitor in a dual setup to another. At very large resolutions, different parts of the engine / hardware are being stressed.
1080p is also a far more common resolution for gaming.
Solution
Use a consistent 1080p with
scale_factor_override: 1.0everywhere.In #9903, this sort of change was added specifically to
bevymarkandmany_cubesbut it makes sense to do it everywhere.Discussion
Maybe we should have a command line option, environment variable, or
CI_TESTING_CONFIGoption for 1080p / 1440p / 4k.Will these look odd (small text?) when screenshotted and shown in the example showcase? The aspect ratio is the same, but they will be downscaled from 1080p instead of ~720p.
Maybe there are other window properties that should be consistent across stress tests. e.g.
resizable: false.Should we add a
stress_test_window(title)helper or something?Bevymark (pre-10472) was intentionally 800x600 to match "bunnymark", I believe. I don't personally think this is very important.