Introduction
The following document describes the minimum recommended system requirements for installing Infinit.e in a production environment.
Server Operating System
Infinit.e is currently tested to run on the following operating systems:
- CentOS 5.5, 5.6, 5.7, 5.8, 6.2, 6.3
- Redhat 5.5, 5.6, 5.7, 5.8, 6.2
- Amazon Linux: 12.08+
Selinux is not supported.
The Infinit.e software and scripts will run on Debian Linux versions such as Ubuntu, but there are not currently any install packages, so the system must be set up by hand. The software will run on Windows, but this is only suitable for testing because the scripts that control the overall platform are Linux-specific.
Server Hardware
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).
The recommended minimum hardware for different scenarios is described below.
We refer to "document" as a catch all for database record, Web page, PDF/office document, XML document etc. The figures below are for some "average" document across all those types ... if most documents ingested are smaller (eg DB records) then the capacity/performance will be higher and conversely if most documents are larger (eg complex pdf reports) then the capacity/performance will be lower.
Demo configuration
For running in a VM on a laptop to demonstrate the tool. May become slow for more than 100-1000 documents.
| 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
A small deployment servicing a few thousand documents:
The following table lists the minimum recommended hardware configuration for one Infinit.e API and Database node.
| 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 + |
Small configuration
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 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) |
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
The following open source software packages are an integral part of the Infinit.e platform:
- Java JRE/JDK 6u30+ (current version = 6u31)
- Apache Tomcat 6.X (current version = 6.0.35)
- MongoDB 2.1+
- elasticsearch 0.19+
Optional Open Source/Free Software
The Infinit.e platform is designed to use Splunk 4.1 for monitoring and reporting of log files. Splunk is a completely optional part of the platform.
Hadoop can be used for batched custom analytics, but is not required.
Client requirements
The Infinit.e GUI (not required for headless configurations) can run on any Linux (Ubuntu, Redhat 6+), Windows XP+, or Mac (10.6+) capable of running the following software:
- Any browser capable of running Flash 11+ (eg Firefox 10+, IE 8+, Chrome 17+)
- Flash 11+