Skip to content
This repository was archived by the owner on Nov 27, 2022. It is now read-only.
This repository was archived by the owner on Nov 27, 2022. It is now read-only.

Use sparse set components for fragmented_iter for Bevy #25

@alice-i-cecile

Description

@alice-i-cecile

As discussed in the 0.5 news release, sparse set component storage was designed to make fragmented iteration faster, precisely the use case being tested in the fragmented_iter benchmark.

Activity

cart

cart commented on Jul 6, 2021

@cart
Collaborator

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 free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @cart@alice-i-cecile

        Issue actions

          Use sparse set components for fragmented_iter for Bevy · Issue #25 · rust-gamedev/ecs_bench_suite