Unity DOTS: C# Job System 

@Dev Kothari 1 dislike ;(

Literally exactly what I need to know as well! Would be really useful if u could do a vid on this (if u haven't already, I haven't checked yet). Another thing I'd be interested in knowing is what the different Ijobs mean. Eg: IjobParalellFor, IjobChunk, etc. The only one I knew before was IjobForEach, but that's outdated now.

Otherwise physics rendering and stuff get desynchronized

That is very much not the case. There's a very high chance you are using jobs by scheduling them and calling Complete() immediately, aren't you? Obviously, Complete() has to wait until the job is complete. The usual way of using jobs efficiently is to schedule them in Update() and Complete() them in LateUpdate() or schedule them in either one of the Update methods and Complete() them the next frame.

more threads used = more power used, higher temperatures, much higher performance

@@n3on440 That might be true, but consider that with the Burst Compiler, you are able to make code that completes the operation needed much faster and thus save energy, especially if you take the time to learn how to correctly use the explicit SIMD vector types like float4 or int3 provide.

Sahab Masroor This was so simple there is no repo. Plus the syntax changes as you go to ECS

Dmitry Osipov Yes this just shows a very basic example to introduce people to the concept and syntax

I thought the exact same thing too when I started to learn to use the job system. I also thought that it is just a weird ThreadPool. But it turns out the Job System is much better for games than Tasks. - The job system does not create any Garbage Collector pressure. When you make a Task, you are making the Task object, the delegate object and possibly the Thread object. Garbage Collection is something you mostly want to avoid in game development. - The job system avoids context switches much much much better than the ThreadPool. If you make 100 Tasks in a frame, they are very likely going to create a lot of OS Threads. The Job system has its worker threads to which it feeds jobs, which makes sure you run into very few context switches as opposed to the ThreadPool. - The job system has the Burst Compiler, which is, hands down, the most powerful feature it boasts. Burst jobs are one of the if not the best way of creating extremely optimized native code that will try its hardest to vectorize itself. Also, with Unity.Mathematics library you can even use explicit SIMD which is amazing. You can even see a very detailed description of how the Burst code compiles in the Burst Inspector.