Should I be worried with these JobHandle.Complete() calls at the beginning of each system? I didn’t call them directly but methods like GetComponentLookup() and GetComponentHandle() call them internally.
#Should I be worried at these internal JobHandle.Complete() calls?
verbal snow
tribal nova
Each JobHandle.Complete will schedule all previously scheduled jobs and make sure the ones with dependencies finish before the system starts. However, from that graph it looks like you don't actually have any jobs running that the JobHandle.Complete runs, so it shouldn't have a performance impact I think?
Do you have any jobs in your game?
verbal snow
I do. I use a job in every system but they don't always execute due to empty query (mostly due to IComponentEnableable). I avoid completing jobs myself but I didn't realize that the API could call them internally.
tribal nova
I do. I use a job in every system but they don't always execute due to empty que...
how many ms do the systems above the jobhandle.Complete take?
tribal nova
Because I'd recommend just setting up a stress-test world and profiling that