Search Unity

  1. Welcome to the Unity Forums! Please take the time to read our Code of Conduct to familiarize yourself with the forum rules and how to post constructively.
  2. Join us on Thursday, June 8, for a Q&A with Unity's Content Pipeline group here on the forum, and on the Unity Discord, and discuss topics around Content Build, Import Workflows, Asset Database, and Addressables!
    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


    Feb 15, 2019
    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


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


    Unity Technologies

    May 18, 2021
    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.