I’m writing some Job code and want to know how its total execution time compares to the managed/main thread code that I’m replacing. Is it fair to wrap the Schedule().Complete() in a timer to get a close idea? Or is calling Complete() immediately going to introduce significant slowdowns over letting the scheduler do its thing across a frame?
Use the timeline view of the profiler when gauging overall saved time, as that will show you the full impact, including scheduling bottlenecks with other jobs.