Introduction
...
| 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 + |
...
The following configuration works quite acceptably on 500K-1M documents. The higher the spec, the faster the performance for a given number/size of documents.
| 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) |
...
Operational configuration
A 3x 2x API node and 2x DB node deployment using the following hardware works very quickly on a 3M2M+ document deployment. In general the system capacity scales fairly linearly with nodes.
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 | 1 2 X Quad Dual Core 1.8+ GHz CPUs 1 | 2 X Quad 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) |
...
The following open source software packages are an integral part of the Infinit.e platform:
- Java JRE/JDK 6u226u30+ (current version = 6u31)
- Apache Tomcat 6.X (current version = 6.0.35)
- MongoDB 2.01+
- elasticsearch 0.1819+
...