Skip to content

Config Groups

Execution Profile config groups enable any specific requirements for a workload to run to be defined. The requirements specified in the config groups are used to control which worker node is used to run the workload.

Four different Config groups can be defined:

  • A Resource Requirements config group, which is used to define the amount of system resources to budget for workloads.

    Defining this config group helps prevent a Worker Node from being overloaded with too many workloads competing for compute resources. Altair SLC Hub restricts the number of concurrent workloads by budgeting compute resource for each workload and allocating workloads to worker nodes guided by the resource requirement values. For more information, see Resource Requirements Config Groups.

  • Resource Limits config group, which is used to define upper limits for CPU and memory usage for workloads.

    Defining this config group ensures that workloads cannot exceed the specified resource limits, helping to enforce resource constraints and maintain system stability. Resource Limits are enforced at the operating system level and provide hard caps for resource usage during execution. For more information, see Resource Limits Config Group.

  • Job Limits config group, which is used to define the maximum number of jobs a user may submit.

    Defining this config group restricts the number of jobs that a particular user may run concurrently. At present, the restriction applies to Link Sessions only. For more information, see Job Limits Config Group.

  • SLC config groups, which are used to define Altair SLC system option requirements for the workload.

    Option values specified in SLC config groups are passed to the Worker Node and enable you to set the behaviour of the Altair SLC engine on which the workload is executed. For more information, see SLC Config Groups.