You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 27, 2022. It is now read-only.
Iterating with the for_each is substantially faster in Bevy as of 0.5.
While many systems will not be written in this way (for loops are great!), performance critical ones will be, which means that it is likely to be more reflective of actual use.
The text was updated successfully, but these errors were encountered:
Yup other ECS-es currently use "fast path" apis, such as SoA insertion and for_each iterators (despite other apis being "more idiomatic" or "recommended"). I think it is fair play at this point to do the same for Bevy.
However this is my current take on ecs_bench_suite policy/labeling in general: #18 (comment)
The current approach biases toward the wrong behaviors and makes it harder for developers to make an informed decision when picking an ECS.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Iterating with the
for_each
is substantially faster in Bevy as of 0.5.While many systems will not be written in this way (for loops are great!), performance critical ones will be, which means that it is likely to be more reflective of actual use.
The text was updated successfully, but these errors were encountered: