Repository navigation
Performance: don't iterate on all archetypes on all queries for new archetypes - #323
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When archetype counts gets too big, we get +10ms total cost each time a new archetype is added, because every query has to scan all archetypes
This adds a version count to Archetypes and a _matchedCount/_matchedVersion to Queries so they can skip the ones they already checked
Would break if anyone edits Archetypes.Items directly I guess
Added claude-generated benchmarks and tests
Fix Archetypes.Clear and index setter not clearing the cache, and queries accidentally returning removed archetypes