You can regulate the performance of the SVM using the resources allocated to it. By default, the following resources are available:
- 2 virtualized processors
- 2 GB of allocated RAM
- 30 GB of allocated disk space
- Virtualized network interface with bandwidth of 100 Mbit/s
- 75 parallel threads of file scan performed on the SVM
When using the default resources, an SVM can interact with 50 to 70 protected virtual machines with average user activity typical for office use.
Over 70 protected virtual machines
If the number of protected virtual machines exceeds 70 or the resources are used more intensively than average, we recommend that you allocate more resources for the SVM.
To estimate the required resources depending on the number of machines, use the following folmulas:
#vCPU = min (#pCPUcore; max (2, #VM/40))
#SvmWorkingThread = #VM*3/2, no less than 50
#RAM = 1 GB + (#SvmWorkingThread - 25)/50
where:
- #vCPU stands for the number of virtualized processors allocated for the SVM
- #pCPUcore stands for the number of physical machines' cores (including those with the Hyper-threading technology)
- #VM stands for the number of protected virtual machines
- #SvmWorkingThread stands for the number of parallel file scan threads on the SVM
- #RAM stands for the volume of RAM allocated for the SVM.
Over 80 protected virtual machines
If the number of protected virtual machines exceeds 80, Kaspersky Lab recommend that you also increase the number of file scan threads: in the [orpc] section of the file /etc/opt/kaspersky/la/ScanServer.conf located on the SVM, specify the required value for the parameter max_processor_threads. For example, you can specify the number that matches the number of protected virtual machines. After you have applied changes, run the command /etc/init.d/la-scanserver restart on the SVM.
By default, while performing scan task, the SVM scans no more than 10 machines at a time. To modify this number in the [ods_scan_queue] section of the file /etc/opt/kaspersky/la/ScanServer.conf located on the SVM, specify the required values for the following parameters:
- max_running_high, which is the number of simultaneously performed scan tasks started manually (high-priority tasks)
- max_running_low, which is the number of simultaneously performed scan tasks started by schedule (low-priority tasks)
Over 256 protected virtual machines
Due to the MAC address allocation issues in Microsoft Windows Server (Hyper-V), you can encounter the problem of overlapping MAC addresses if a hypervisor serves more than 256 virtual machines. Thus, the connection between protected machines and the SVM may be unstable. To eliminate the problem, expand the range of dynamically allocated MAC addresses and make sure that MAC addresses of all protected virtul machines are unique on the respective hypervisors.
Over 500 protected virtual machines
If the number of protected virtual machines on the hypervisor exceeds 80, additional hypervisor configuration may be required. For more information, please contact Technical Support.
