Examples
Example 1 | Worker |
|
Execution service mapping |
|
|
Resource group |
|
|
Scheduling | A maximum of 2 concurrent jobs will be scheduled on the worker. | |
Example 2 | Worker |
|
Execution service mapping |
|
|
Resource group |
|
|
Scheduling | A maximum of 4 concurrent jobs will be scheduled on the worker, each with 4 threads assigned. Each job should consume no more than 4 threads. | |
Example 3 | Worker |
|
Execution service mapping |
|
|
Resource group |
|
|
Scheduling | Up to 256 concurrent jobs will be scheduled on the worker. Each job should consume no more than 4 threads. | |
Example 4 | Worker |
|
Execution service mapping |
|
|
Resource group |
|
|
Scheduling | A maximum of 32 concurrent jobs will be scheduled on the worker. Each job should consume no more than 1 thread. | |
Example 5 | Worker |
|
Execution service mapping |
|
|
Resource group |
|
|
Scheduling | A maximum of 4 jobs will be scheduled on the worker. Each job should consume no more than 1 thread. | |
Example 6 | Worker |
|
Execution service mapping |
|
|
Resource group |
|
|
Scheduling | Up to 256 jobs can be scheduled on the worker, each consuming no more than 2 threads. However, no jobs will be scheduled on the worker if the worker is already running any job that specifies a memory requirement. |
© 2001-2024 Fair Isaac Corporation. All rights reserved. This documentation is the property of Fair Isaac Corporation (“FICO”). Receipt or possession of this documentation does not convey rights to disclose, reproduce, make derivative works, use, or allow others to use it except solely for internal evaluation purposes to determine whether to purchase a license to the software described in this documentation, or as otherwise set forth in a written software license agreement between you and FICO (or a FICO affiliate). Use of this documentation and the software described in it must conform strictly to the foregoing permitted uses, and no other use is permitted.