James Liu b508b5c7c7 Skip empty archetypes and tables when iterating over queries (#4724) ... # Objective Speed up queries that are fragmented over many empty archetypes and tables. ## Solution Add a early-out to check if the table or archetype is empty before iterating over it. This adds an extra branch for every archetype matched, but skips setting the archetype/table to the underlying state and any iteration over it. This may not be worth it for the default `Query::iter` and maybe even the `Query::for_each` implementations, but this definitely avoids scheduling unnecessary tasks in the `Query::par_for_each` case. Ideally, `matched_archetypes` should only contain archetypes where there's actually work to do, but this would add a `O(n)` flat cost to every call to `update_archetypes` that scales with the number of matched archetypes. TODO: Benchmark		2022-10-24 13:22:05 +00:00
..
benches	Skip empty archetypes and tables when iterating over queries (#4724)	2022-10-24 13:22:05 +00:00
Cargo.toml	ECS benchmarks organization (#5189)	2022-07-04 14:17:45 +00:00