Deadline Slave without GUI using all CPU resources on Mac

Hi,

I just got new 3.1 release and i’m testing it on 2 machines, one is intel quad machine other is dual core.

So to get to the point…I recently discovered the deadlineslave -nogui flag, which starts deadline in console/shell mode, but when started in such way DeadlineSlave (or to be more precise mono) starts eating cpu cycles. On quad machine that means 100% of one core.

I’m trying to minimize the performance hit by running slaves in console if possible but this seems like bug on mac os release.

Great release though, i was waiting long time for mac version, since i think this is one of the easiest and most efficient render managers out there…

Cheers!

I checked the Mono bug list and it looks like this is due to a known Mono bug. I’m sure we can find a way to work around it for now, and include this in the next release. Thanks for bringing this to our attention!

Cheers,

  • Ryan