Search Unity

  1. Unity 6 Preview is now available. To find out what's new, have a look at our Unity 6 Preview blog post.
    Dismiss Notice
  2. Unity is excited to announce that we will be collaborating with TheXPlace for a summer game jam from June 13 - June 19. Learn more.
    Dismiss Notice

Resolved Netcode: One Entity with Sync'ed Buffer Elements vs Many Entities with Sync'ed Single Component Data

Discussion in 'DOTS Dev Blitz Day 2022 - Q&A' started by Kmsxkuse, Dec 8, 2022.

  1. Kmsxkuse

    Kmsxkuse

    Joined:
    Feb 15, 2019
    Posts:
    306
    As I go back the drawing board for my data synchronization, what sort of entity structure should I develop. Assuming that memory is infinite, should I have a shallow entity structure where each entity contains a single float component or a deeper structure with an entity representing a float in multiple buffer elements?
     
  2. TheOtherMonarch

    TheOtherMonarch

    Joined:
    Jul 28, 2012
    Posts:
    886
    Obsessively buffer element has overhead. It depends on if you need to do stuff like sorting.
     
  3. NikiWalker

    NikiWalker

    Unity Technologies

    Joined:
    May 18, 2021
    Posts:
    329
    Apologies, as mentioned in the other post, it's unfortunately not something we can easily answer. To even begin to, we'd need significantly more context about your data, requirements, limits, and project, and even then, our answer would be static (i.e. it couldn't adapt over time with your project).

    The fundamentals of compression (entropy) are constant, so I'd recommend you start from those "first principles". Even the assumption that this is the bottleneck, is unverifiable right now. I'd recommend prototyping a few different ideas to build a bigger picture. We'd likely be able to give more specific advice then, too.
     
    Kmsxkuse likes this.