Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use the Continuous update mode in stress tests when unfocused #11652

Merged

Conversation

Kanabenki
Copy link
Contributor

Objective

  • When running any of the stress tests, the refresh rate is currently capped to 60hz because of the ReactiveLowPower default used when the window is not in focus. Since stress tests should run as fast as possible (and as such vsync is disabled for all of them), it makes sense to always run them in Continuous mode. This is especially useful to avoid capturing non-representative frame times when recording a Tracy frame.

Solution

  • Always use the Continuous update mode in stress tests.

@Kanabenki Kanabenki added C-Examples An addition or correction to our examples C-Usability A targeted quality-of-life change that makes Bevy easier to use labels Feb 1, 2024
@alice-i-cecile alice-i-cecile added C-Bug An unexpected or incorrect behavior C-Benchmarks Stress tests and benchmarks used to measure how fast things are and removed C-Usability A targeted quality-of-life change that makes Bevy easier to use labels Feb 1, 2024
@matiqo15 matiqo15 added the S-Ready-For-Final-Review This PR has been approved by the community. It's ready for a maintainer to consider merging it label Feb 1, 2024
@alice-i-cecile alice-i-cecile added this pull request to the merge queue Feb 1, 2024
Merged via the queue into bevyengine:main with commit e3cf5f8 Feb 1, 2024
29 checks passed
tjamaan pushed a commit to tjamaan/bevy that referenced this pull request Feb 6, 2024
…engine#11652)

# Objective

- When running any of the stress tests, the refresh rate is currently
capped to 60hz because of the `ReactiveLowPower` default used when the
window is not in focus. Since stress tests should run as fast as
possible (and as such vsync is disabled for all of them), it makes sense
to always run them in `Continuous` mode. This is especially useful to
avoid capturing non-representative frame times when recording a Tracy
frame.

## Solution

- Always use the `Continuous` update mode in stress tests.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-Benchmarks Stress tests and benchmarks used to measure how fast things are C-Bug An unexpected or incorrect behavior C-Examples An addition or correction to our examples S-Ready-For-Final-Review This PR has been approved by the community. It's ready for a maintainer to consider merging it
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants