I’ve got a really large job dependency tree that kicks off a bunch of jobs that take a long time to finish. I’m okay with them blocking the main thread on the next frame, when I need to kick off the next batch of jobs, that is expected. However, it seems the main thread is blocked until well after my jobs have completed?
Strangely, “Graphics Jobs” in the options seems to affect this behavior. Here is a picture of my profiler’s timeline without graphics jobs being enabled.
And here is a picture of my profiler’s timeline WITH graphics jobs being enabled.
Any ideas why this behavior is as such? If the profiler is telling me the truth, my jobs have finished awhile ago. However, I have a feeling that my jobs are actually taking longer than the profiler is telling me, mostly because I see a big gap in my jobs (there’s probably actually one the system is waiting on?). There’s a sort of fence between the two batches of blue, but its still just one Complete I call on the next frame.