Page 1 of 1

networking slave fail

Posted: Sat May 23, 2015 6:34 am
by Scottiefeng
Hi guys,

Tried networking on small scene, all working well.

But did not work for bigger scene. Always report 'slave fail'

Same version 2.3.2.2 standalone on wired networking.

Did anyone has got the same issue? It defeats the purposed of networking rendering.

Thanks

Re: networking slave fail

Posted: Sat May 23, 2015 7:05 am
by Scottiefeng
I also figure out the slave fails when the scene is over about 2000MB.

The office networking is on 1G wired.

Re: networking slave fail

Posted: Sat May 23, 2015 8:08 am
by Scottiefeng
The daemon slave shows that not hear the core beat then kill itself.

Re: networking slave fail

Posted: Wed May 27, 2015 12:43 pm
by BorisGoreta
Do your GPUs in slave have enough GPU memory ?

If on your main box you have a dedicated display GPU which is not use for Octane rendering then the rest of the GPUs in the main box can use all GPU memory.

In the network node most probably you don't have a dedicated display GPU which means that all GPUs in that node will not have all GPU memory available.

Maybe that is why the node sometimes fail on bigger scenes.

Re: networking slave fail

Posted: Thu May 28, 2015 9:09 am
by abstrax
Another reason could be the driver timeout on Windows, see here and here.

Re: networking slave fail

Posted: Mon Jun 01, 2015 3:39 pm
by Scottiefeng
abstrax wrote:Another reason could be the driver timeout on Windows, see here and here.
Thanks guys.