CPU usage when idle

[Raveen.Rajadorai]

Hello, 

We're on Motionbuilder 2018.0.2 right now and we're noticing that MB is using roughly 10% of the CPU constantly, even on an empty scene. The strange thing is that when you open multiple MB it shares this load over those processes, so if you had three open each of them would roughly use 3%.

Is there any solution to this? 

Motionbuilder 2017 does not seem to suffer from this. 

Thank you
Kind regards, 
Ray

EDIT: It looks like motionbuilder is using a lot of resources for "swap" according to the profiling center. Any idea why?

[lee.dunham]

Huh, thats interesting - haven't noticed that yet. I will take a look tomorrow and ask around.

At a guess, I'd assume its a single shared process for Motionbuilder processes to utilise, which would account for the lack of increase with additional Motionbuilders being launched.

No idea what it would be though. Will post if we find anything.

[Raveen.Rajadorai]

Hey Lee,

Awesome! Thank you for looking into it. 

It is strange, it doesn't seem to happen in earlier versions of Motionbuilder. 
All I could find is motionbuilder doing something with the swap space even when Idle, and it was using a fair amount of CPU usage for it. 

[lee.dunham]

When I checked, it only used a chunk of CPU whilst the application was expanded/visible. CPU was much lower when the application was minimized.

But I also found the same results, approx 10% CPU for n number of instances (with reason)