Introduction
...
The minimum required hardware depends on the volume of data that will be ingested. Note that new nodes can always be added to scale in either storage or performance. Similarly, lower spec configurations (or combining API and Database nodes) will usually work but will start to provide significantly degraded performance (and of course no more data can be ingested once the storage space runs out).
...
Infinit.e API + DB Node | |
---|---|
Processor | 1x 1.8+ GHz CPU |
Memory | 1 or 2 GB RAM |
Network | WAN connection/none |
Storage | 20GB |
Compact configuration
...
Infinit.e API + DB Node | |
---|---|
Processor | 1 X Dual/Quad Core 1.8+ GHz CPUs |
Memory | 4-8 GB RAM |
Network | 1x GigE LAN connection |
Storage | 10 GB Root/OS partition + |
...
Infinit.e API Node | Infinit.e Database Node | |
---|---|---|
Processor | 1 X Dual Core 1.8+ GHz CPUs | 1 X Dual Core 1.8+ GHz CPUs |
Memory | 8-16 GB RAM or more | 8-16 GB RAM or more |
Network | 2x GigE LAN connection | 2x GigE LAN connection |
Storage | 15 GB Root/OS partition + (~5GB per 1 million documents) | 15 GB Root/OS partition + (~10GB per 1 million documents) |
...
Infinit.e API Node | Infinit.e Database Node | |
---|---|---|
Processor | 1 X Quad Core 1.8+ GHz CPUs | 1 X Quad Core 1.8+ GHz CPUs |
Memory | 16 GB RAM or more | 16 GB RAM or more |
Network | 2x GigE LAN connection | 2x GigE LAN connection |
Storage | 20 GB Root/OS partition + | 20 GB Root/OS partition + 100+ GB data partition, RAID-0 (~10GB per 1 million documents) |
...