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 + (~5GB per 1 million documents) | 15 GB Root/OS partition + (~10GB per 1 million documents) |
...
A 2x API node and 2x DB node deployment using the following hardware works very quickly on a 2M+ document deployment. In general the system capacity scales fairly linearly with nodes (see below).
This is the minimum recommended operational configuration because it provides data redundancy across the nodes as well as separating the API and DB functions, which is important for performance.
| 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 + 100+ GB data partition, RAID-0 (~10GB per 1 million 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. |
Required Open Source Software
...