Difference between revisions of "Old Legacy Server Sizing"
Kevin Wilkie (Talk | contribs) |
Kevin Wilkie (Talk | contribs) |
||
Line 13: | Line 13: | ||
|- | |- | ||
! Data Type | ! Data Type | ||
− | ! Space Per Record | + | ! Min Space Per Record |
|- | |- | ||
| Forensics Flow | | Forensics Flow | ||
Line 22: | Line 22: | ||
|- | |- | ||
| Event Record | | Event Record | ||
− | | | + | | 900Bytes |
|} | |} | ||
For raw flow storage allow of 250bytes per flow | For raw flow storage allow of 250bytes per flow |
Revision as of 12:56, 30 September 2016
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.
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. The addition of a hardware raid controller supporting Raid 10 or at least Raid 5 will also improve performance and provide hardware redundancy. The mount 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 |
For raw flow storage allow of 250bytes per flow
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.