13-04-2020, 08:13 AM
Hi there,
I'm unable to reproduce this. This is how the profiler looks like simulating a single short rope for me:
VSync On:
![[Image: XgQmNbJ.png]](https://i.imgur.com/XgQmNbJ.png)
VSync Off:
![[Image: v5YJ3TG.png]](https://i.imgur.com/v5YJ3TG.png)
No spikes whatsoever. Similar behavior in Windows 7, macOS Catalina and Ubuntu Linux.
Internally Obi uses a thread pool to implement a task scheduler. Threads need to be woken up when new tasks are available, the time taken for a thread to go to sleep is dynamically adjusted based on the workload (more work, more idle time before going to sleep). Might be that in your architecture, threads take longer to be woken up after being put to sleep, but without more info that's just a shot in the dark.
What Platform, CPU, Unity and Obi versions are you using to test this?
I'm unable to reproduce this. This is how the profiler looks like simulating a single short rope for me:
VSync On:
VSync Off:
No spikes whatsoever. Similar behavior in Windows 7, macOS Catalina and Ubuntu Linux.
Internally Obi uses a thread pool to implement a task scheduler. Threads need to be woken up when new tasks are available, the time taken for a thread to go to sleep is dynamically adjusted based on the workload (more work, more idle time before going to sleep). Might be that in your architecture, threads take longer to be woken up after being put to sleep, but without more info that's just a shot in the dark.
What Platform, CPU, Unity and Obi versions are you using to test this?