bevy/examples/stress_tests
Pablo Reinhardt d96a9d15f6
Migrate from Query::single and friends to Single (#15872)
# Objective

- closes #15866

## Solution

- Simply migrate where possible.

## Testing

- Expect that CI will do most of the work. Examples is another way of
testing this, as most of the work is in that area.
---

## Notes
For now, this PR doesn't migrate `QueryState::single` and friends as for
now, this look like another issue. So for example, QueryBuilders that
used single or `World::query` that used single wasn't migrated. If there
is a easy way to migrate those, please let me know.

Most of the uses of `Query::single` were removed, the only other uses
that I found was related to tests of said methods, so will probably be
removed when we remove `Query::single`.
2024-10-13 20:32:06 +00:00
..
bevymark.rs Migrate from Query::single and friends to Single (#15872) 2024-10-13 20:32:06 +00:00
many_animated_sprites.rs Migrate from Query::single and friends to Single (#15872) 2024-10-13 20:32:06 +00:00
many_buttons.rs split up TextStyle (#15857) 2024-10-13 17:06:22 +00:00
many_cubes.rs Migrate from Query::single and friends to Single (#15872) 2024-10-13 20:32:06 +00:00
many_foxes.rs Deprecate SpatialBundle (#15830) 2024-10-13 17:28:22 +00:00
many_gizmos.rs Migrate from Query::single and friends to Single (#15872) 2024-10-13 20:32:06 +00:00
many_glyphs.rs split up TextStyle (#15857) 2024-10-13 17:06:22 +00:00
many_lights.rs Migrate from Query::single and friends to Single (#15872) 2024-10-13 20:32:06 +00:00
many_sprites.rs Migrate from Query::single and friends to Single (#15872) 2024-10-13 20:32:06 +00:00
README.md Add a stress test profile (#6901) 2022-12-20 15:59:41 +00:00
text_pipeline.rs split up TextStyle (#15857) 2024-10-13 17:06:22 +00:00
transform_hierarchy.rs Deprecate get_or_spawn (#15652) 2024-10-07 16:08:22 +00:00
warning_string.txt Added performance warning when running stress test examples in debug mode (#5029) 2022-07-13 19:13:46 +00:00

Stress tests

These examples are used to stress test Bevy's performance in various ways. These should be run with the "stress-test" profile to accurately represent performance in production, otherwise they will run in cargo's default "dev" profile which is very slow.

Example Command

cargo run --profile stress-test --example <EXAMPLE>