Using ECB justified here?

Unity Engine
,
1

Might be a silly question. Case: server gets initialized and creates ServerInitialized entity. Other systems require it for update. Is there any reason to create that entity in the end of frame ECB? I kinda like the idea of creating all entities in one sync point as long as one frame delay is not a problem, but is there any benefit to it in simple cases like that?

Is the only benefit of ECB in not stalling any jobs that read or write the same components?

2

ECB playback is burst-compiled. For non-frequent or single-entity initialization code, ecb is not really necessary, just put the initialization system right before or after a barrier and just use EntityManager. Profiling your own code/setup will identify sync point issues.

1 Like
3

Here are two of the main reasons to use an ECB (as a general rule for all ECB operations not just when spawning entities):

  1. You do not want to create an additional sync point.
  2. You do not want some logic / change to occur until a certain sync point.

In this particular case I don’t see any real advantage or disadvantage in using an ECB.

2 Likes