Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Introduction

...

  • CentOS 5.5
  • Redhat 5.5, 5.6, 5.7, 5.8

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 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. 

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
Memory1 or 2 GB RAM
NetworkWAN 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   
Memory4-8 GB RAM
Network1x GigE LAN connection
Storage

10 GB Root/OS partition +
50 GB data partition  

Small configuration

The following configuration works quite acceptably on 

 Infinit.e API NodeInfinit.e Database Node
Processor 2 1 X Quad Code Dual Core 1.8+ GHz CPUs    2 1 X Quad Code Dual Core 1.8+ GHz CPUs 
Memory8-16 GB RAM or more8-16 GB RAM or more
Network2x GigE LAN connection2x GigE LAN connection
Storage

40 15 GB Root/OS partition +
100 20 GB data partition, RAID-0

(~5GB per 1 million documents)  

40

15 GB Root/OS partition +

100

50 GB data partition, RAID-0

(~10GB per 1 million documents)

Note 1: It is possible to combine API and DB nodes onto one physical server however the minimum recommended configuration would include two or more servers (one each for API and DB).

...

Large configuration

A 3x API node and 2x DB node deployment using the following hardware works very quickly on a 3M+ document deployment.

 Infinit.e API NodeInfinit.e Database Node
Processor 1 X Quad Core 1.8+ GHz CPUs    1 X Quad Core 1.8+ GHz CPUs 
Memory16 GB RAM or more16 GB RAM or more
Network2x GigE LAN connection2x GigE LAN connection
Storage

20 GB Root/OS partition +
50+ GB data partition, RAID-0
(~5GB per 1 million documents)  

20 GB Root/OS partition +
100+ GB data partition, RAID-0
(~10GB per 1 million documents)

Required Open Source 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.