Message-ID: <1010950569.8827.1711700954808.JavaMail.confluence@host3.pipelinefx.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_8826_1526949517.1711700954808" ------=_Part_8826_1526949517.1711700954808 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html How to limit the number of renders on a host

How to limit the number of renders on a host

The easiest thing to do is to submit your jobs with a memory res= ervation. The reservation will force the Supervisor to look for hosts with = the requisite amount of memory before dispatching the job, and then block o= ut (or reserve) the amount requested. This will serve to limit the number o= f subjobs running on the host to only the number that it can safely handle.=

For example, say your hosts have 4 subjob slots and 2GB of memory. If ea= ch render process or thread needs 1GB or memory, you will soon overtax the = machine because you will have 4 subjobs each asking for 1GB or more.

If you add a resource reservation (in MB) when you submit the job:

host.memory=3D1000

Then you will only have at most 2 subjobs running on the host, because t= hat's as much memory as it can handle. Memory is a resource, so you should = be able to monitor it in the QubeGUI by selecting a Worker and examining th= e Properties tab, under host resources.

You can also restrict jobs by limiting the number subjobs per host on a = per job basis. If you have hosts with 4 subjob slots, you can just send eac= h job a resource reservation of:

host.processors=3D4

However, if you have a mix of hosts with different numbers of subjob slo= ts, then you would need to do something like this:

host.processors=3D1+

This will reserve a minimum of 1 slot per subjob, up to the maximum numb= er of slots on the host. This won't guarantee a host will have multiple sub= jobs, so you may need to investigate the other options above.

You could reconfigure each host to have only one subjob slot per host. T= o do this, you will need to log in to the Worker and use the Configuration = tool. Go to Worker Settings, then Advanced settings and set the Worker CPUs= to 1.

Create a limited resource on each host. For example, if you're working w= ith Maya render jobs, you can create a Maya worker resource with a quantity= of 1 per Worker. You'll need to use the Configuration tool, select Worker = Settings, then Worker Configuration. Add a Resource called host.maya Worker= resource, and a Total of 1.

When you submit the job add this reservation:

host.maya=3D1

More information on resources and using the Configuration GUI can be fou= nd in the Administration manual.

------=_Part_8826_1526949517.1711700954808--