the documentation isn’t specific about this so I assume a bursted job ran with Run() gets burst benefit, wanted to check.
If you are talking about Entites.Foreach or Job.WitCode than yes. Unless you are executing .WithoutBurst() method on it
AFAIK yes, it runs Bursted as long as the Job has the BurstCompile attribute. You could profile to be sure about that.
benchmark done. it does. from 6ms to .4ms
Yes. Bursting is a separate construct from the jobs parallelism! Burst simply turns the block of code into the assembly goop and makes things ideally perform better by using smarter instructions i.e. allowing you to process an array with vectorized instructions as opposed to individual instructions for each array entry. Utilizing Run() runs the code synchronously on the main thread where Schedule() and ScheduleParallel() allow you to run code asynchronously off the main thread.