more than one DRSpawner-progress on one server ?

[sso_cg]

hello,

two weeks ago my design studio bought a dual-xeon-quadcore rendering server with 16gb ram and so on ...

We use Rhino with Vray for designing yachts.

Now the problem:
one of our working places starts a rendering with vray and the DRSpawner on the server. All 8 render buckets work fine but we have other working places .. what when another workingplace will start a rendering, too ??
Is there a possibility to split the power of the server when necessary to more than one render progress?

I think for example on vmware ?

And we have many computers, which do nothing more than email and so on ..
I tried the DRSpawner for using them to support the Server. But there is the same problem.
The first render progress got all power.
Is there any server tool, which can share the renderslaves ?

Friendly greetings ...

[dalomar_cg]

Re: more than one DRSpawner-progress on one server ?

The spawner can only contribute to one render at a time. If you have other machines that are just doing email, then you could have spawners on those and send jobs specifically to those machines. Is that what your asking?

[sso_cg]

Re: more than one DRSpawner-progress on one server ?

hello dolmar,
that is, what we did.

But we want to render two or three pictures at the same time, using the same network.

How can we share the power so that not just one render progress get all power ?

I know we can specify the machines for the distributed rendering. But it is no solution to edit that settings before each rendering.

There should be something automatically, which share the machines for the distributed rendering...

that for example the first rendering get 100% network power.
After a while a secound rendering is starting and than a tool shares the power that both processes get 50%.

[dalomar_cg]

Re: more than one DRSpawner-progress on one server ?

The spawners are just meant to help out with a rendering. What your asking is for the spawners to be managed and have a knowledge of what they're working on, along with what they could be working on. In short, we're just not there yet with the spawners and it will most likely require separate managing application. There's nothing preventing you from sending several images to different sets of render slaves, but it would have to be from different instances of Rhino and would have to specify which servers would work on an image. Right now we're in the early stages of working on our next full version, and rethinking the spawners is something that will get attention. I'll add these comments to the wishlist and see what we can do for getting these in there.

[sso_cg]

Re: more than one DRSpawner-progress on one server ?

hi dolomar,
it would be really great if the new version is more dynamical.

For example:
I have two workingplaces and each one starts a rendering.
Now the first one gets all network power of DRSpawners, so that its picture will be rendered very quickly.
After the first workingplace+DRSpawners finish their work, the secound workingplace doesnt get the Networkpower because it doesnt query for more DRSpawner while rendering on its own.

The really best solution would be a DRSpawner-manager which manage the whole DRSpawner network. It means, that the query for rendering slaves have to be sent to only one server and not to each slave. Now the Server decide, how many slaves will be used for this progress.
With a network interface you should be able to set up the preority of currend rendering tasks or specify how many slaves should work on them.


With that feature we will order some new versions as soon as possible !!


Is there a release date of the new version ? Or will there be a beta-test period ?

Thanks to your fast reply !

[dalomar_cg]

Re: more than one DRSpawner-progress on one server ?

We'll see as to how dynamic it winds up being, but if it could achieve the process you described that would be great. We don't have any set release date because there's too much that has to happen between here and there, but its more likely to be towards the last third of this year. We'll likely have some sort of beta period for current customers before its released, but thats not something that's going to happen in the near future. We'll keep every body posted.