Plixer Scrutinizer core system¶
This section covers the resource requirements to support the Plixer Scrutinizer core product.
Standalone deployments¶
The following tables show the recommended CPU core count and RAM allocations for a standalone Plixer Scrutinizer Collector with only its main functions enabled (flow collection, aggregation, reporting, and the web interface).
CPU cores
Exporters |
|||||||||
5 |
25 |
50 |
100 |
200 |
300 |
400 |
500 |
||
Flows/s |
5k |
4 |
|||||||
10k |
8 |
||||||||
20k |
16 |
||||||||
50k |
32 |
||||||||
75k |
46 |
||||||||
100k |
52 |
||||||||
125k |
58 |
||||||||
150k |
64 |
Memory/RAM (GB)
Exporters |
|||||||||
5 |
25 |
50 |
100 |
200 |
300 |
400 |
500 |
||
Flows/s |
5k |
8 |
|||||||
10k |
16 |
||||||||
20k |
32 |
||||||||
50k |
64 |
||||||||
75k |
96 |
||||||||
100k |
128 |
||||||||
125k |
160 |
||||||||
150k |
192 |
Distributed clusters (reporting Collector only)¶
In distributed Plixer Scrutinizer environments, additional load is placed on the reporting server based on the number of Collectors in the cluster.
The following table shows the additional resources required to support the added load:
Minimum |
Recommended |
|
---|---|---|
CPU |
2x the number of Collectors in the cluster |
4x the number of Collectors in the cluster |
RAM |
2 GB per server in the cluster |
4 GB per Collectors in the cluster |