2 ms·
If you take out ordering, then lookups on your SoA are now a search, and n-field lookup on an entity is now a JOIN operation. The smarter you get about it, the
by setr 4mo ago
If you take out ordering, then lookups on your SoA are now a search, and n-field lookup on an entity is now a JOIN operation.
The smarter you get about it, the closer you get to an OLAP db
Which leads to my theory… I feel like Bevy could be implemented on top of an in-memory DuckDB and get away with it
- Altern4tiveAcc 4mo agoDepending on your access patterns, maybe you could have a hash table mapping entities ids to indexes in your SoA. Perhaps that's viable if looking up a single entity is not typical to your use case? > Which leads to my theory… I feel like Bevy could be implemented on top of an in-memory DuckDB and get away with it Haha, it certainly does sound viable.