Slave CPU Affinity

Deadline
1

Hi All:

I edit slave setting like CPU affinity through command line,
but the repository needs 3-4 mins to pick up the new slave setting.
is there a command or python can force it to update immediately?

Thank you all

Jen

2

Hi,
You could restart the slave and this will force the update to be pushed through immediately.
Cheers,
Mike

3

Hi, Mike:

Thanks for reply,
Yes, restart slaves can force update,
but is there a way to do that not involving restart slave?

4

No, unfortunately not.

Are you trying to re-jig your slave settings on a kind of per job type going through your farm. ie: some jobs run better with a few CPU’s and others need ALL the CPU’s? Hence, your using the command line to edit slave CPU affinities ‘on the fly’?

If so, the current recommended way to achieve the same result, would be to run multiple slaves on 1 machine, with each slave having different CPU affinity settings. Then, apply say, a different pool/group setting to each slave, so it picks up only certain targeted jobs in your queue.

I’ll put a feature request onto the wish-list for a “slave settings API force immediate update” function.

5

Hi Mike:

Thank you so much for replying,

I am trying to communicate deadline with my server, so when someone log in a machine it will automatically set the CPU affinity to half,
Upon log out it will set CPU affinity back to full automatically.
set up pools seems a great alternative way, I will test it.
If you have others smart ways to do it, please share with me,

thank you

Jen

6

Hi Jen,
Just to let you know that in Deadline 6.1, the slave now invalidates its settings before it looks for its next task. So, if you change the slave settings, it will pick up the new settings before it picks up the next task. Deadline v6.1 will be released very soon.
Mike