...
One load configuration architecture for development (exists only in the Developer Edition ISO file).
The Developer Edition ISO file name is DPOD-Developer-CentOS-<version>.iso, and can be downloaded from Fix Central.Five load configuration architectures for the Standard Edition, available as:
Appliance Mode (ISO file) - DPOD_CentOS_<version>.iso - can be downloaded from PPA.
Non-Appliance Mode (Compressed Executable file) - DPOD_RedHat_<version>.cef - can be downloaded from PPA.
It is not possible to change the load configuration architecture after DPOD is installed. In order to change from one architecture to another, a new installation of DPOD is required, discarding the old data collected so far.
Please consider the following rules of thumb for sizing:
...
Available in Edition | Load Configuration Architecture | Goal | TPS Limit(7) | Supports Virtual Environment | Cores | RAM | Storage |
|---|---|---|---|---|---|---|---|
Developer | Development | Developers only. In rare cases can be used for functional POCs. Under restricted license. | 2-3 TPS | Can be virtual (5) | 2 cores (1) | 4 GB (3) | Single disk: 25GB |
Standard | Minimal | POCs and evaluation. | 5 TPS | Can be virtual (5) | 4 cores (1) | 18 GB (3) | OS: 40 GB |
Standard | Low | Environment with low load levels | 40 TPS | Can be virtual (5) | 6 cores (1) | 32 GB (3) | OS: 40 GB |
Standard | Medium | Environment with moderate load | 80 TPS | Can be virtual (5) | 8 cores (1) | 64 GB (3) | OS: 40 GB |
Standard | High | Environment with moderate load | 120 TPS | Can be virtual, but not recommended (5) | 16 cores (1) | 128-256 GB (3) | OS: 40 GB |
Standard | High_20dv | Environment with medium to high load | 200-1500 TPS (6) | Must be installed on a physical server | Needs sizing (6) | Needs sizing (6) | Needs sizing (6) |
Standard | High_20dv | Environment with very high load | 2750 TPS (6) | Must be installed on a physical server | Needs sizing (6) | Needs sizing (6) | Needs sizing (6) |
Standard | Environment with very high load | >2750 TPS - TBD (6) | Must be installed on physical servers | Needs sizing (6) | Needs sizing (6) | Needs sizing (6) |
...
(6) Customers will be provided with specifications after a sizing process with L3.
(7) If TPS is too high and DPOD is unable to process all the incoming messages, some will be dropped, causing DPOD to show unreliable data (some transactions might not appear, some errors might not be displayed, some data such as latency might be missing from some of the transactions, etc.). When messages are dropped, an internal alert is generated and displayed in DPOD Web Console (under DPOD Health → Internal Alerts).
Storage Requirements
DPOD is I/O intensive, as it needs to persist all logs and information at very high rates. Therefore, it needs to be configured with very fast disks, and with at least 3 separate disks (OS, app/logs, data).
Some configurations, such as the Cell environment, require additional data disks.
Usage of slow disks will impact the maximum TPS that DPOD can process, the performance of queries and the amount of time between the creation of transaction logs and the availability of the data on DPOD's dashboards.
For each 1 TB of data 64 GB of RAM is recommended for responsive queries (dashboards and filters).
NFS is not supported for the data disk, as the Store relies on file system behavior that NFS does not supply. Data corruption and other problems can occur.
Software RAID (such as CentOS built-in RAID) is not supported.
The data disk retention is automatically managed by DPOD. For each type of data (transactional, resources, payload, etc.), once its quota is full, old data will be discarded to make room for new data of the same type. A bigger disk size will hold a longer history.
...