Question on how to Share Distributed Bucket Rendering::

[samsaleem]

HI,

 

i have a setup of Distributed Bucket Rendering (DBR) and its working perfectly alright, BUT,

 

if one person is rendering on the nodes, and in the mean time second person is submitting the job for render, so when the first person finishes the render job, the second person is not able to pick the slave render nodes at the end of first persons render job,

 

is there any work around for this issue ??

 

regards

 

Saleem

[Devin Johnston]

You can't use the same machines to render two different things at the same time, this is a bad idea.

[samsaleem]

well i dont want them to render at the same time actually

 

example

member XX started render at time : 11:00am and i took control of all nodes and its going

member YY started render at time : 11:30am and he could not take control and as of now his local machine is working

 

Member xx finished render at 11:45am,

 

now render nodes are free .. so in this case .. can member YY take control of nodes ?? as the rendering has started already in network mode - and connections are made successfully and i can see its connecting and active session but not rendering.

 

regards

 

Saleem

[Devin Johnston]

In this case member YY shouldn't be able to use the nodes after member XX is fished because the workstation member YY is working at has already begun the rendering process and once that has started I don't think there's any way to get the nodes to catch up.

[BrianKitts]

I've found DR to get really finicky....it'll start dropping or not picking up jobs if you are working on scenes and you have it switching back and forth between different jobs. So if we have two people using the nodes, then we'll just split them in half and turn off the other persons nodes in the DR settings.

[Devin Johnston]

We do the same thing.

[notamondayfan]

I think if you manually close the vray spawners on your nodes and restart them, then YY's render should start.

 

Other than that, use DR with net-render (back burner) and que your jobs in there.

[samsaleem]

@maxer : i wish there was a work around

 

@Brian : for a smaller team its practical, but if there is bigger or even medium team then its not that practical .. or atleast for me its not that productive as i m sharing this between a team of 4 designers, and they have a regular testing renders going, so say a farm of 12 nodes shared for them means actually 3 nodes for each, and that will actually hamper the actual productivity.

@Notamondayfan : thats a good idea, i am trying to write a script where it can help me automate restarting the spawner - as i m running as a service so i may be able to do that with some tools,

 

about backburner : i have not tried it much, but i think its good for rendering animation and we are working on still images, and we are using VRAY,

 

VRAY 2.0.1 - for last few days i am trying to setup a test farm with vray 2.0 i hope this gives me some solution as i can see if there is a rendering going on and if i start a node in between it catches up with rendering, and there is an option of restart of rendering nodes at the end of rendering .. but that option has given me bad time previously - i hope this time it helps me good when go back to office,

 

any input on vray 2.0 ?? and its new approaches ??

[notamondayfan]

@maxer : i wish there was a work around

 

about backburner : i have not tried it much, but i think its good for rendering animation and we are working on still images, and we are using VRAY,

 

 

Backburner is much more than a tool for rendering animations. It will stop your team from trying to use rendernodes when they shouldnt be. It also means you can stack up renders over night, and you can easily see the render times, resolution, etc.

 

For testing, I find that 1 good workstation is usually good enough, and I will submit drafts to backburner when it's needed. If your team needs 5 nodes to test, then I would look at why they need so much power and see if there are ways to streamline their pipeline. The guys in my team know not to watch buckets and only render what's needed.

[samsaleem]

about the question of teams requirement ..

 

We are working as a construction design firm, and our team is working in preparing 3D models for big buildings and their interior designing as well and usually ending to high resolution image rendering -

 

i will be working on back burner now and will see if it improves any thing