...
Available in Edition | Load Configuration Architecture | Goal | TPS Limit(74) | 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: 30GB |
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 TPS (6) | Must be installed on physical servers | Needs sizing (6) | Needs sizing (6) | Needs sizing (6) |
...
(4) The TPS is the maximum total transaction transactions load across all devices/domains connected to DPOD.
(5) Virtual deployments performance cannot be guaranteed. Virtual deployments performance depends on the server hosting the VM (ESX), its configuration, the overall load it is experiencing at any given time from any of its VMs, and especially the performance of the remote storage.
(6) Customers will be provided with specifications after a sizing process with L3.
(7) If If the 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).
(5) Virtual deployments performance cannot be guaranteed. Virtual deployments performance depends on the server hosting the VM (ESX), its configuration, the overall load it is experiencing at any given time from any of its VMs, and especially the performance of the remote storage.
(6) Customers will be provided with specifications after a sizing process with support L3 team.
Storage Requirements
DPOD is I/O intensive, as it needs to persist all logs and information at very high rates. Therefore, for most of the installations, 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.
...
CentOS 7.7-7.9 - x86-64 bit only on supported HW or Hypervisor as stated above.
RHEL 7.7-7.9, 8.3 - x86-64 bit only on supported HW or Hypervisor as stated above.
Server The OS must be a fresh install, without any other installed products.
In Non-Appliance mode the The OS support is not covered, but recommendations will be provided.
Third-party software such as antivirus, cybersecurity, monitoring, APM, endpoint protection, backup, etc. might significantly decrease the performance of DPOD and impact its functionality. During the resolution of issues, DPOD support will ask the customer to disable any 3rd party software in order to isolate the issues and verify their source. Support cannot be provided if the 3rd party tools are not disabled.
...