11-05-2021, 09:13 AM
(This post was last modified: 11-05-2021, 01:15 PM by josemendez.)
The jobs debugger affects any Burst code in your project, not just Obi. It's funny when you think DOTS motto is "performance by default", however in-editor performance is terrible by default, since the debugger re-enables itself every single time. I will consider adding this warning in upcoming updates, just to save the suprise to anyone that's not used to Burst. Thanks! 
There's lots other stuff in the editor that can affect performance. Having the profiler enabled also eats away 5-10% performance, having deep profiling enabled will very negative affect performance too, etc. These affect any code running in editor, not just Obi.
Also be mindful of your timestep settings. Unity's default max fixed timestep (0.33) is very prone to causing death spiraling on physics intensive scenes. I generally recommend setting it to 2-3 times your fixed timestep. So if you are using a timestep of 0.02, set max fixed timestep to 0.04-0.06. That will ensure 2 or 3 physics steps are done per frame, not more.
There's lots other stuff in the editor that can affect performance. Having the profiler enabled also eats away 5-10% performance, having deep profiling enabled will very negative affect performance too, etc. These affect any code running in editor, not just Obi.
Also be mindful of your timestep settings. Unity's default max fixed timestep (0.33) is very prone to causing death spiraling on physics intensive scenes. I generally recommend setting it to 2-3 times your fixed timestep. So if you are using a timestep of 0.02, set max fixed timestep to 0.04-0.06. That will ensure 2 or 3 physics steps are done per frame, not more.