Initial Deadline Setup Issues & Help Required

Sure @Justin_B get that, and that’s very useful info.

My apologies if I should be posting this to some other topics and threads, but since I am new both to Deadline itself as well as these forums, a few quick questions:

  1. For already submitted jobs - how do we edit its “Job Info Parameters” as well as its “Plugin Info Parameters”?

  2. How can we edit the already submitted Gaffer job to add the “-threads 16” parameter to it? and how can we get the respective job’s execution also to pick it up and respect that flag for the actual command line execution?

  3. Can we have the Job’s “Concurrent Tasks” be a dynamic or programmatically calculated value? For example, for the Deadline-Gaffer job, we want to drive this through the job’s submission parameter “-threads int” value. And hoping to implement it in a way like the one below:

where the goal is to send concurrent jobs on a Deadline worker(s) with heterogeneous cores of machines (which would be say a mix of 16,32,72 and 128 cores) - where the job’s requested rendering thread counts should assign multiple concurrent jobs to a deadline worker, where

-threads 16

on a 16 core worker - it should assign/run one job/task
on a 32 core worker - it should assign/run two concurrent jobs/tasks
on a 72 core worker - it should assign/run four concurrent jobs/tasks
on a 128 core worker - it should assign/run eight concurrent jobs/tasks

this is what I am exploring right now,

Thanks,
Bhavik