set_job_process_concurrency_limit

This command sets the job process concurrency limit.

Guardium can run multiple threads in parallel to optimize the performance and utilization of the CPU. To take advantage of this multi-threading feature, use the set_job_process_concurrency_limit command. This command defines the number of assessment and classifier processes that can run concurrently.

This API is available in Guardium V10.6 and later.

GuardAPI syntax

set_job_process_concurrency_limit parameter=value

Parameters

Parameter Value type Description
limit Integer Required.

The limit value defines the number of assessment and classifier processes that can run concurrently. The limit value is the lesser of 100 or twice the number of CPU cores installed on the Guardium system.

For example, if a system has 8 CPU cores, the maximum limit value is 16. If a system has 64 CPU cores, the maximum limit value is 100.

The default limit value is 1.

api_target_host String

Specifies the target hosts where the API executes. Valid values:
  • all_managed: execute on all managed units but not the central manager
  • all: execute on all managed units and the central manager
  • group:<group name>: execute on all managed units identified by <group name>
  • host name or IP address of a managed unit: specified from the central manager to execute on a managed unit.  For example, api_target_host=10.0.1.123.
  • host name or IP address of the central manager: specified from a managed unit to execute on the central manager. For example, api_target_host=10.0.1.123.

IP addresses must conform to the IP mode of your network. For dual IP mode, use the same IP protocol with which the managed unit is registered with the central manager. For example, if the registration uses IPv6, specify an IPv6 address. The hostname is independent of IP mode and can be used with any mode.

Examples

grdapi set_job_process_concurrency_limit limit=10