How does DRSpawner work?

[doelay]

Hi all..

I am setting up a new rendering farm (from my current 2 PCs with Dual Quad Core Xeons) to an additional two i7 PCs. If I have DRSpawner running on 2 of the slave PCs, with the other 2 PCs acting as masters sending jobs to the slave PCs, how does DRSpawner handle requests. Does it lock up DRspawner until it finishes the buckets of just one frame, or does it lock it up until the actual job is done from master PC1. I don’t want to slow a rendering down while the second master is waiting for master1 to finish the rendering using the slave.

Thanks.

[dkendig]

Re: How does DRSpawner work?

If you kick off a render, our plugin will communicate with the machines that you specify in our render options. If the DR Spawner is up and running on those machines, it will be sent a render job, and the DR Spawner will start the render sequence and send off the finished chunks of your render as it goes, until the completion of that sequence. After it's done a sequence, it's ready to receive a new job. When you start a render, if one of the DR Spawners you specify is busy, it will not be used for that render sequence. If a DR Spawner becomes available during the render, it still is going to be ignored, because it wasn't available when we asked the DR Spawners if they were busy when the render sequence was started.

If you're doing an animation, Rhino and Sketchup behave a little differently. With Rhino we treat every frame as a different render sequence, and in SketchUp we treat the entire animation as a render sequence. If you play around with it a little bit, I think you'll see what I'm talking about.

[doelay]

Re: How does DRSpawner work?

Thanks for the info.

cheer