Help ObiSolver.Lateupdate() bad performance

[josemendez]

Thanks, think i got it!


Also figured out the IL2CPP performance issue apparently was because i was using "debug" compiler configuration - which normally is not an issue, but may have big implications for Obi.

"debug" compiling is always a lot slower, since it skips code optimizations. This is not a big deal for simple stuff, but as soon as you have performance-sensitive code this can become huge.

Edit: same applies to deep profiling, since it adds timing markers to every function call making the code significantly slower. This happens at compile time. A common pitfall is making a build with "deep profiling support" enabled, but assuming it will run fast as long as you don't connect the profiler and enable "deep profiling". Since the markers are introduced when compiling the code, the resulting build will be slow regardless of using deep profiling or not.