DR and Backburner

[tricky]

All our render machines always have Backburner running on them. If I also decide to run Vrayspawner on them and run a DR job from my workstation, and then a network render job is submitted to Backburner, which takes priority?

Another way of putting this would be:

Is there a way to always tell Backburner to take priority, and for DR only to use processors that are not busy? (I don't want colleagues complaining that I am nicking their processor time!)

[Dynedain]

Not really.

I posted a script a while back (it's also on scriptspot somewhere) that sets the priority of max to low on startup if its running in server mode (aka, backburner or DR). But specifying at that level which has higher priority I don't think is possible, since they both have the same windows priority level.

[Da_elf]

what we need is a script that looks on the computers and tells you whats being used. not whats running thats easy to tell if the spawner is running. whether its running or being used is a different matter. Suppose you had two work liscences for vray and on a farm of 10 computers you would want to be able to remotely see if the other dude is using the computers for a DR or not. backburner tells us if a system is already engaged in a backburner process when you submit a job. (or you can pul up the backburner monitor) we should have something like this for vrays DR

[Dynedain]

But what he wants is the next level beyond that, for backburner or vray DR to be able to tell if the other is in active use or not.

[dbuchhofer]

that would be very helpful in the 'early testing' portions of jobs.. though truthfully, for me as a final render, split scanlines has overtaken dr for usefulness and stability easy.