vrayspawner60 slowing down backburner?

I have searched the forum, but cannot find an answer, mainly because I don’t know the right terms, I guess.

I have two identical machines.
One is the workstation the other one is the render slave.
I startet vrayspawner as a service on the render slave.

Now if I render some animation with backburner the render slave renders half the time longer for the same image:
workstation 10min
renderslave: 15min

I found t hat if I disable the vrayspawner service both computers render in farly the same time (± some seconds).

I also noticed that sometimes there is a second copy of 3dsmax running that is accumulation memmory. If I kill it through the taskmanager, its starts again and starts grabbing memmory.

Is this normal behaviour?

Ok. As currently every try of using distributed rendering produces only trash (mixed up buckets from various scenes) I can savely disable the spawener.

I am using vray advanced 1.5RC2 I guess.

Georg

this happens to me as well, also looking for answers…

I also noticed that sometimes there is a second copy of 3dsmax running that is accumulation memmory. If I kill it through the taskmanager, its starts again and starts grabbing memmory.

The starting of the 2nd MAX is caused by the Spawner itself.
You should kill the Spawner , not the MAX.

Keep in mind, when doing BB, let go OFF what you don’t need. So, if
no Spawner is needed - go stop it.

Best regards,
nikki Candelero

also the priority set might come into affect. For example if bb will require 100% of cpu at a given time, and at that time spawner will also require 100% of cpu, then it will be a lag, so setting spawner for priority belownormal will force the bb to have 100% of cpu, then spawner can get the rest, when bb is done.

Thank you for your answers.

I will try the priority tip after finishing my current project.
I sounds like this version could scale to a render farm with more than two computers.

Georg

yuo can also run the spawner as a service which will kill the max instance once its finished, which frees up the computer for BB

The spawner was running as a service.
Somehow it was triggered and started doning something.
There was no simultanios DR / BB rendering on this machine.

Georg