Reduce memory usage from Edges #20784
Draft
+75
−64
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.
Objective
The
SparseArray
inEdges
uses a lot of memory forSolution
Edges
to useHashMap
instead.HashMap
s on a combination of the source archetype and the bundle.Edges
to the top level ofWorld
instead of individualArchetypes
This should result in the memory usage in
Edges
across a world scaling linearly with the number of observedArchetype
moves instead of scaling quadratically with the number of archetypes.TODO: Benchmark
Testing
CI
Future Work
If desirable, we may want to move the TypeId lookup into Edges, keying on
(ArchetypeId, TypeId)
instead. It'd return the associated BundleId and skip the Bundles typemap lookup.