The following tables provide suggested system requirements based on on-premises gateway performance test results.
|
CPU |
RAM |
Feature Set |
Network Throughput |
HTTP Transactions per Second |
Recommended Active User Number |
|---|---|---|---|---|---|
|
4 cores, 8 threads |
16 GB |
Cloud Access Rules only |
650 Mbps |
5,100 |
2,200 |
|
4 cores, 8 threads |
16 GB |
Cloud Access Rules with Threat Protection |
530 Mbps |
4,100 |
1,700 |
|
4 cores, 8 threads |
16 GB |
Cloud Access Rules with Threat Protection and Data Loss Prevention |
310 Mbps |
2,300 |
1,000 |
|
12 cores, 24 threads |
64 GB |
Cloud Access Rules only |
860 Mbps |
6,700 |
2,800 |
|
12 cores, 24 threads |
64 GB |
Cloud Access Rules with Threat Protection |
760 Mbps |
5,800 |
2,400 |
|
12 cores, 24 threads |
64 GB |
Cloud Access Rules with Threat Protection and Data Loss Prevention |
540 Mbps |
4,100 |
1,700 |
|
Number of vCPU Cores |
RAM |
Feature Set |
Network Throughput |
HTTP Transactions per Second |
Recommended Active User Number |
|---|---|---|---|---|---|
|
12 |
32 GB |
Cloud Access Rules with Threat Protection |
330 Mbps |
2,500 |
1,800 |
-
The traffic model was 80% HTTPS traffic and 20% HTTP traffic.
-
20 Data Loss Prevention templates were enabled and used.
-
The performance indexes dropped about 5% when syslog forwarding was enabled.
|
Total User Number |
Log Retention Time |
Recommended Disk Size |
|---|---|---|
|
1,000 |
30 days |
275 GB |
|
2,000 |
30 days |
470 GB |
|
5,000 |
30 days |
1,055 GB |
|
10,000 |
30 days |
2,030 GB |
The TMWS on-premises gateway keeps logs for up to 180 days. The system will automatically purge logs if disk usage exceeds 80%.