Introduction
...
| Infinit.e API + DB Node | |
|---|---|
| Processor | 1x 1.8+ GHz CPU |
| Memory | 1 or 2 GB RAM (swap required to get up to ~8GB total) |
| 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 (swap required to get up to ~8GB total) |
| Network | 1x GigE LAN connection |
| Storage | 10 GB Root/OS partition + |
...
| Infinit.e API Node | Infinit.e Database Node | |
|---|---|---|
| Processor | 1-2 X Dual Core 1.8+ GHz CPUs | 1-2 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 + (~10GB per 1 million "average" documents) | 15 GB Root/OS partition + (~60GB per 1 million "average" documents) |
...
A 2x API node and 2x DB node deployment using the following hardware works very quickly on a 2M+ document deployment (eg 2M-5M is a good typical range). In general the system capacity scales fairly linearly with nodes (see below).
...
| Infinit.e API Node | Infinit.e Database Node | |
|---|---|---|
| Processor | 2 X Dual Core 1.8+ GHz CPUs | 2 X Dual Core 1.8+ GHz CPUs |
| Memory | 16 GB RAM or more (32GB is ideal) | 16 GB RAM or more (32GB is ideal) |
| Network | 2x GigE LAN connection | 2x GigE LAN connection |
| Storage | 20 GB Root/OS partition + | 20 GB Root/OS partition + 600+ GB data partition, RAID-0 (~60GB per 1 million "average" documents) |
| Info |
|---|
Note the DB scales per 2-node block, since the primary benefit of the second node is redundancy rather than performance - although it balances the reads somewhat (not the writes) so there is some (not 2x) performance gain within a replica set. |
Record server
From Sep 2014, the Infinit.e platform also supports smaller, lightweight "records" - ingested via Logstash and viewed via our Kibana integration. We estimate that 2 API nodes (eg a 4-node cluster; though DB nodes don't matter) can handle 5M records a day with a 30 day retention, so 150M total.
Required Open Source Software
...