Message-ID: <741581985.8641.1711693991498.JavaMail.confluence@host3.pipelinefx.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_8640_1259759794.1711693991497" ------=_Part_8640_1259759794.1711693991497 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html Specifying a Worker's Job Slots

Specifying a Worker's Job Slots

The maximum number of job instances that a Worker can run is spe= cified by the worker_cpus paramet= er.  This value can be set in either the worker's local qb.conf file, = or the centrally= -managed qbwrk.conf file.

By default, Qube sets the number of job slots equal to the number of CPU= cores on the system.  

=20
=20 Icon=20
Hyper-threaded cores are seen as a core, so a machine with 12 physical cor= es that has hyper-threading enabled and worker_cpus=3D0 will be configured = with 24 job slots.=20
=20
=20
=20 Icon=20
=20

If the usage of your farm will exclusively consist of jobs that are expe= cted to run as many threads as there are cores in the system (multi-threade= d rendering often can auto-detect the number of cores), it is often advisab= le to set the maximum number of processes that a Worker can run to 1 instea= d of the maximum number of cores since multi-threaded processes themselves = can automatically take advantage of all available cores; this an applicatio= n-specific solution, and is commonly used with AfterEffects, Cinema4D, Maya= software renderer, mentalray, pixar RenderMan, etc. When configured this w= ay, your users will never have to ensure that the job's slot reservations m= atch the thread count.

=20
=20
=20

In this example, = set the number of job slots to 2:

worker_cpus =3D 2

 

 

------=_Part_8640_1259759794.1711693991497--