29-05-2020, 11:16 AM
(This post was last modified: 29-05-2020, 11:31 AM by josemendez.)
Hi there,
I was unable to reproduce the spikes using your sample project. Tried on 3 different machines:
- PC (Windows 10, Corei7 4771, 3.5Ghz 8 cores)
- Mac Pro (mid-2016)
- Mac Book Air (2014)
The profiler looks very similar in all 3:
![[Image: xz8gVzg.png]](https://i.imgur.com/xz8gVzg.png)
Edit: Out of luck, I was able to reproduce the spikes in Windows by having Chrome open and playing a couple videos on the background:
![[Image: gpUJ95y.png]](https://i.imgur.com/gpUJ95y.png)
Obi spawns one thread less than the CPU's max thread count, up to a maximum of 7. Since Chrome is heavily multithreaded too, many logic threads could be fighting for CPU time, forcing Obi to wait for its threads to be given some CPU time. This would of course happen with any other multithreaded application, not just Chrome. Unfortunately there's not much we can do to prevent this, as cpu time must be shared among all threads running.
I was unable to reproduce the spikes using your sample project. Tried on 3 different machines:
- PC (Windows 10, Corei7 4771, 3.5Ghz 8 cores)
- Mac Pro (mid-2016)
- Mac Book Air (2014)
The profiler looks very similar in all 3:
Edit: Out of luck, I was able to reproduce the spikes in Windows by having Chrome open and playing a couple videos on the background:
Obi spawns one thread less than the CPU's max thread count, up to a maximum of 7. Since Chrome is heavily multithreaded too, many logic threads could be fighting for CPU time, forcing Obi to wait for its threads to be given some CPU time. This would of course happen with any other multithreaded application, not just Chrome. Unfortunately there's not much we can do to prevent this, as cpu time must be shared among all threads running.