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
networking slave fail
Forum rules
Please add your OS and Hardware Configuration in your signature, it makes it easier for us to help you analyze problems. Example: Win 7 64 | Geforce GTX680 | i7 3770 | 16GB
Please add your OS and Hardware Configuration in your signature, it makes it easier for us to help you analyze problems. Example: Win 7 64 | Geforce GTX680 | i7 3770 | 16GB
- Scottiefeng

- Posts: 183
- Joined: Fri Aug 01, 2014 1:46 pm
I also figure out the slave fails when the scene is over about 2000MB.
The office networking is on 1G wired.
The office networking is on 1G wired.
- Scottiefeng

- Posts: 183
- Joined: Fri Aug 01, 2014 1:46 pm
The daemon slave shows that not hear the core beat then kill itself.
- BorisGoreta

- Posts: 1418
- Joined: Fri Dec 07, 2012 6:45 pm
- Contact:
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.
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.
- Scottiefeng

- Posts: 183
- Joined: Fri Aug 01, 2014 1:46 pm
