Feedback Burst job schedule overhead

[josemendez]

Well, "huge" is relative term, I mean that my job struct is not even half as big as this one, but took way longer to schedule:

That's 22 arrays and a few integers/floats, which totals around a bit more than 176 bytes (22*2*4 bytes), let's say 200. Copying 200 bytes is basically instant, should not even show up in a profiler. If your job is copying around larger structs (even if it looks smaller code-wise) then it will be slower to schedule. Note that schedule overhead also depends on other factors, not just struct size.

In any case you are right, disabling debugger removed stacked overhead, shame there is no button in editor and I need script for that.

There's a button for this: you can find it in either Jobs->Jobs debugger or in Preferences->Jobs->Enable Jobs Debugger.
If you want to measure performance in editor, you should leave it disabled. See "Performance" of the Burst backend in Obi's manual:
https://obi.virtualmethodstudio.com/manu...kends.html

Additional question - I noticed before that particle collision job is completed instantly and blocks main thread for very long time, is it possible to avoid this?

Not currently, since other jobs depend on it (including, but not limited to fluids). For Obi 8 I'm aiming to remove all Complete() calls mid-step.

kind regards,