21-11-2023, 08:27 AM
(This post was last modified: 21-11-2023, 08:32 AM by josemendez.)
(20-11-2023, 07:57 PM)Henning Wrote: Hi Obi team!
I have been trying to improve the time performance of my project recently with the Unity profiler.
One significant part of the CPU usage (40-50%) was under Obi fixed updater, "semaphore. wait for signal". As shown in the attached image.
Hi,
There's no image attached to your post. Either paste a link to it, or attach the file to the post (make sure you press "AddAttachment" after dragging the file!).
(20-11-2023, 07:57 PM)Henning Wrote: I did some googling and it seems like that updater was waiting for the frame to be rendered? Just want to confirm this is correct and I should work on simplifying the rendering process.
Not at all, "wait for signal" just means the main thread is waiting for something. Could be rendering, could be physics, AI, input, literally anything, depends on the context. If it's happening in FixedUpdate(), a safe guess would be it's waiting for other threads that are performing physics simulation.
Check other threads in the profiler, see if they're doing any work while the main thread waits. If they are, it means the main thread is waiting for them to finish so your focus should be on optimizing whatever those other threads are doing.
kine regards,