We test against the latest Mozilla Firefox, MicroSoft Edge and Google Chrome browsers.
See here for a useful server size calculator.
GigaFlow has been tested and certified to support up to 1,000 concurrent devices or up to 40,000 flows per second (flow/s) from less than 20 devices.
The flow rate changes with the number of connected devices as follows:
Flow/s | Number of Devices |
---|---|
50,000 | 10 |
40,000 | 20 |
20,000 | 40 |
10,000 | 80 |
5,000 | 160 |
2,500 | 300 |
1,250 | 600 |
1,000 | 1,000 |
Allow for at least 600 bytes per flow record per second for I/O throughput, i.e.
Flow/s | Bytes/s (Sustained Write Performance) | MB/s (Sustained Write Performance) |
---|---|---|
100 | 60,000 | 0.06 |
2,000 | 1,200,000 | 1.2 |
10,000 | 6,000,000 | 6.0 |
40,000 | 24,000,000 | 24.0 |
With
f = flow/s
d = number of devices
I = Input/Output performance measurement (IOP), nominally sustained sequential writing.
I = 20 + (f / 500) + (d / 5)
i.e. allow for a base of 20 IOPs, add an additional 1 IOP/s for every 500 flow/s and another 1 IOP/s for every 5 devices.
Flow/s | Number of Devices | IOPs |
---|---|---|
1,000 | 1,000 | 222 |
5,000 | 1,000 | 230 |
10,000 | 100 | 60 |
40,000 | 10 | 102 |
Allow for at least 100 IOPs read.
The server must support at least 300 MB/s sustained read and write to handle the peak device or flow count. Anything less than this will result in dropped flows. For Linux, we recommend EXT4 or XFS file systems as well a dedicated RAID partition for the database. Adding a hardware RAID controller that supports RAID 10, or at least RAID 5, will improve performance and provide hardware redundancy. The amount of storage required is directly related to the flow rate and features enabled.
Data Type | Minimum Space Per Record (Bytes) |
---|---|
Forensics Flow | 250 |
Event Record | 900 |
500 flow/s of forensics == 450 MB per hour == 11 GB disk space per day.
A basic installation should have 4 GB RAM available for the OS and additional 50 MB per device to monitor. More RAM will always improve performance:
Number of Devices | Minimum RAM (GB) |
---|---|
10 | 4.5 |
100 | 9 |
500 | 29 |
1,000 | 54 |
CPU sizing in GigaFlow is based on the Postgre SQL database. Overall performance is also dependent on CPU performance.
While there is little to gain by going beyond 8 cores, more powerful CPUs will provide a better experience. Intel's Xeon X5680 3GHz or Core i7-3770S 3GHz are recommended as a minimum required specification.
As a demonstration, GigaFlow was installed on a typical server with the following specifications:
The results of a performance test were as follows:
Devices | Flows | Total Flows | CPU Idle | Disk Write | IO Writes | Disk Utilisation | Notes |
- | per device s-1 | - | % | MB s-1 | s-1 | % | - |
10 | 15,000 | 15,0000 | 80 | 88 | 250 | 9 | |
50 | 3,000 | 150,000 | 78 | 91 | 260 | 11 | |
100 | 1,500 | 150,000 | 78 | 91 | 261 | 11 | At limit of flow cache before flows are dropped. |
250 | 400 | 100,000 | 85 | 62 | 142 | 5 | Must double RAM used by GigaFlow to 1,536 MB. |
500 | 200 | 100,000 | 86 | 58 | 190 | 10 | Must double RAM used by GigaFlow to 1,536 MB. |
1,000 | 100 | 100,000 | 85 | 59 | 232 | 10 | Must double RAM used by GigaFlow to 1,536 MB. |
2,000 | 50 | 100,000 | 82 | 59 | 220 | 10 | Must double RAM used by GigaFlow to 1,536 MB. |
These results show that this relatively mid-specification machine can cope with 50 devices at 150K flows per second. The same system can handle 2,000 devices with a cumulative count of 100K flows/s.
We recommend a maximum of 1,000 devices per GigaFlow server. Above this, database query performance will degrade.
Yes, there is a REST endpoint for all report data with a portal user definitions to control access. You can open your GigaFlow system for integration with third party applications.
For more information, see API articles at the official GigaFlow Wiki.
No, your GigaFlow system is accessed via a HTML/Javascript front-end using your preferred browser. Output is rendered as HTML, .csv or .pdf.
© Copyright 2019 Anuview. All rights reserved. VIAVI and the VIAVI logo are trademarks of VIAVI Solutions Inc. ("VIAVI"). All other trademarks and registered trademarks are the property of their respective owners. No part of this guide may be reproduced or transmitted, electronically or otherwise, without the written permission of the publisher.
Reproduction and distribution of this guide is authorized for Government purposes only.