You can set a limit on CPU usage for scan tasks. No limit is set by default. You can also configure memory usage limits for scan tasks. The default limit is 8192 megabytes.
Setting a limit in the Web Console
In the Web Console, you can enable and disable the CPU utilization limit and configure the memory usage limit for scan tasks in the policy properties (Application settings → General settings → Application settings, Performance section).
Settings
Setting |
Description |
|---|---|
Memory usage limit for scan tasks (MB) |
Input field for the memory usage limit for scan tasks (in megabytes). Default value: 8192. |
Limit CPU usage by scan tasks (%) |
The checkbox enables or disables the CPU utilization limit for the Malware Scan, Critical Areas Scan, Inventory, and Container Scan tasks. If the check box is selected, the maximum utilization of all processor cores will not exceed the number specified in Upper limit (%). This check box is cleared by default. |
Setting a limit in the Administration Console
In the Administration Console, you can enable and disable the CPU utilization limit and configure the memory usage limit for scan tasks in the policy properties (General settings → Application settings, Performance section).
Under Performance, clicking the Configure button opens the CPU and memory usage window, in which you can configure limits (see the table below).
Settings
Setting |
Description |
|---|---|
Limit CPU usage for scan tasks (%) |
The checkbox enables or disables the CPU utilization limit for the Malware Scan, Critical Areas Scan, Inventory, and Container Scan tasks. If the check box is selected, the maximum utilization of all processor cores will not exceed the percentage specified in the field on the right. This check box is cleared by default. |
Memory usage limit for scan tasks (MB) |
Input field for the memory usage limit for scan tasks (in megabytes). Default value: 8192. |
Setting a limit on the command line
In the command line, you can configure CPU utilization limits for ODS, ContainerScan, and InventoryScan tasks using the UseOnDemandCPULimit and OnDemandCPULimit settings in the general application settings.
You can edit the setting using command line options or a configuration file that contains all general application settings.
UseOnDemandCPULimit accepts the following values:
Yes: enable the CPU usage limit for ODS, ContainerScan, and InventoryScan tasks.No: disable the CPU usage limit for tasks.The OnDemandCPULimit option sets the maximum utilization level for all processor cores (as a percentage) when running ODS, ContainerScan, and InventoryScan tasks. The option accepts values between 10 and 100. Default value 100.
In the command line, you can configure memory usage limits for ODS, ContainerScan, and InventoryScan tasks using the ScanMemoryLimit setting in the kesl.ini configuration file. Default value: 8192.