This is probably an easy fix (hopefully), and I think its to do with network bandwidth, but I didn’t have enough time to troubleshoot before I left the office. Basically I have 26 nodes rendering a 5k image; each did the required 5 or 6 passes in about 8min, but it took nearly an hour for all the data to get to the master machine and finish the render.
Should I reduce the max number of pixels transported or increase the time between sends? Or both?
This worked pretty well, down to 27 minutes so only about ~17 minutes of it grabbing data from other nodes. Though I’m having another issue with all my render elements that might be prolonging this. I’ll make a separate post for it.
Yeah, this was how 1.1 was working for us, I just thought it was one of the changes to distributed rendering in 1.2 or 1.3.
Just to be clear this is how the render happens: The master machine renders 5 passes (the total required passes are 125, so I’m assuming that it knows the other 25 machines will do 5 passes as well), another window pops up saying collecting data from slaves, at this point, the master machine stops rendering (cpu usage drops down under 20%). Then for the rest of the time, it is just collecting data from the slaves. All 26 machines are the same, so they all finish their 5 passes around the same time.