datastore: early exit missing components at table level #1554
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.
This is a partial fix for #1545: it takes care of the
O(n)
backward walk when querying for non-existing components, but it doesn't explain why there are that many buckets in the first place when running theclocks
example (that's another problem for another PR).Bench:
![image](https://user-images.githubusercontent.com/2910679/224278674-8987a4da-7f5b-45fa-abdc-712066efb91e.png)
clocks
in debug: