The server requirements for RAM and hard drive capacity are determined based on the node performance value derived from the estimated hardware requirements (see the table below).
Server RAM and hard drive capacity
Node performance, Mbps |
RAM, GB |
Hard drive capacity, GB |
RAID type |
Minimum spin rate of the disk subsystem of the hypervisor or physical server, revolutions/min |
Maximum cache size, GB (only for a Standalone installation) |
Maximum size of Syslog event log files, GB (only for a Standalone installation) |
0–90 |
16 |
200 |
— |
7200 |
3 |
15 |
90–180 |
22 |
250 |
— |
7200 |
6 |
35 |
180–270 |
28 |
300 |
— |
10,000 |
9 |
60 |
270–360 |
34 |
350 |
— |
10,000 |
12 |
90 |
360–450 |
40 |
400 |
— |
10,000 |
15 |
120 |
450–540 |
46 |
450 |
10 |
10,000 |
18 |
150 |
540–630 |
52 |
500 |
10 |
10,000 |
21 |
180 |
630–720 |
58 |
550 |
10 |
10,000 |
24 |
210 |
720–810 |
64 |
600 |
10 |
10,000 |
27 |
230 |
The hard drive capacity indicated in the table is applicable if the drive is partitioned into a root partition and a swap partition corresponding to the amount of available RAM.
If you are using Kaspersky Web Traffic Security (Standalone), prior to running a virus scan, the application saves the contents of all transmitted files to the /tmp folder. To reduce the load on the disk subsystem, you can do one of the following:
It is recommended to use the following values for the caching settings:
The value for the maximum cache size is provided in the table above. It is specified in bytes.
You can enable logging of traffic processing events, system events of the application, and Kaspersky Anti Targeted Attack Platform server file transfer events to a Syslog event log. If you are using Kaspersky Web Traffic Security (Standalone), when enabling logging you need to do the following on the operating system side:
The value for the maximum size of log files is provided in the table above.