Difference between revisions of "Old Legacy Server Sizing"
Kevin Wilkie (Talk | contribs) |
Kevin Wilkie (Talk | contribs) |
||
Line 14: | Line 14: | ||
1000 1000 | 1000 1000 | ||
+ | |||
+ | '''Disk Throughput''' | ||
+ | Allow for at least 500 bytes per flow record per seconds for IO throughput | ||
+ | e.g. 100 flows/s = 1000*500 = 50000=0.5MB/sec of write performance required. | ||
+ | 2000 flows/s = 2000*500 = 1000000 = 1MB/s of write performance required. | ||
'''Disk Sizing''' | '''Disk Sizing''' |
Revision as of 10:34, 30 August 2018
Anuview Flow has been tested and certified to support up to 1000 concurrent devices or up to 40k flows/s from < 20 devices.
Below we can see as more devices are added to the system, the supported flow rate decreases in proportion.
Flows/s Devices 50000 10 40000 20 20000 40 10000 80 5000 160 2500 300 1250 600 1000 1000
Disk Throughput
Allow for at least 500 bytes per flow record per seconds for IO throughput
e.g. 100 flows/s = 1000*500 = 50000=0.5MB/sec of write performance required. 2000 flows/s = 2000*500 = 1000000 = 1MB/s of write performance required.
Disk Sizing The server must support at least 300MB/s sustained for both read and write to support the peak device or flow count. Failing to do so will result in dropped flow details. For Linux, the recommendation would be to use EXT4 or XFS file systems and have the database on it's own raid partition. The addition of a hardware raid controller supporting Raid 10 or at least Raid 5 will also improve performance and provide hardware redundancy. The amount of storage required is directly related to the flow rate and what features are enabled.
Data Type | Min Space Per Record |
---|---|
Forensics Flow | 250bytes |
FlowSec Flow | 150Bytes |
Event Record | 900Bytes |
e.g 500 flow/s of forensics = 450MB per hour = 11GB of disk space per day.
RAM Sizing
A base installation should have 4GB or RAM available for the OS and and additional 50MB per device to monitor. More ram will always improve performance
e.g
Number Of Devices | Min Ram |
---|---|
10 | 4.5GB |
100 | 9GB |
500 | 29GB |
1000 | 54GB |
CPU sizing As Anuview Flow is based on the Postgres database, overall performance is also dependent on CPU performance.
There is little gain going beyond 8 cores however more powerful CPUs would provide a better experience. Intel XeonX5680 3GHz or Core i7-3770S 3GHz would be recommended as a minimum.