Versions Compared

Version Old Version 77 New Version Current
Changes made by

Amit Munwes

Amit Munwes

Saved on

Key

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

...

  • RHEL v8.3-v8.10, v9.4 - x86-64 bit only on supported HW or Hypervisor as stated above.

  • Rocky Linux v8.3-v8.10, v9.4 - x86-64 bit only on supported HW or Hypervisor as stated above.

  • Some maintenance or advanced configuration tasks requires root or a user capable of running the sudo command (e.g. installation, upgrade, backup and restore of the DPOD application).

  • Review the Operating System Requirements for Non-Appliance Mode and work with your Linux team to configure the OS properly.

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

...

  • For up to 120 TPS (across all devices), choose one of the Developer/Standard options from the table below.

  • For over 120 TPS (across all devices), complete a sizing process by opening a support ticket with IBM Support.

  • A single installation of a DPOD cell environment with 7 physical cell members can process up to ~20,000 TPS (assuming ~35 ~50 Syslog records per transaction on average). For a higher load, consider creating several installations.

...

  • It is not possible to change the deployment profile after DPOD is installed. In order to change from one deployment profile to another, a new installation of DPOD is required, discarding the old data collected so far.

  • 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. This may result with a lower or higher performance for the same resources in different environments.

  • It is recommended to conduct a performance test to determine the actual performance on your specific environment.

...

Edition

Deployment Profile

Goal

Expected TPS Limit(4)

Virtual / Physical

Cores

RAM

Storage

DPOD Simulator

Development

May be used for demonstrationDemonstration, development and evaluation only.

3 TPS

Runs as several Several containers

8 cores (1)

12 GB (3)

25 GB free space in the Docker working directory (/var/lib/docker)

Docker Container for Developer

Development

May be used for demonstrationDemonstration, development and evaluation only.

3 TPS

Runs as a containerContainer

2 cores (1)

5 GB (3)

6 GB free space in the Docker working directory (/var/lib/docker)

Developer

Development

May be used for demonstrationDemonstration, development and evaluation only.

3 TPS

Virtual server

2 cores (1)

5 GB (3)

Single disk: 60 GB

Standard

Minimal

POCs and evaluation.

5 TPS

Virtual server

4 cores (1)

18 GB (3)

Single disk(6): 200-400 GB

OR

3 disks:
OS: 50 GB
App/Logs: 100 GB
Data: 100-300 GB

Standard

Low

POCs, evaluation, and environments with low load levels

40 TPS

Virtual server

6 cores (1)

32 GB (3)

3 disks:
OS: 50 GB
App/Logs: 100 GB
Data(2): 100-1000 GB

Standard

Medium

Environments with moderate load

80 TPS

Virtual server

8 cores (1)

64 GB (3)

3 disks:
OS: 50 GB
App/Logs: 100 GB
Data(2): 300-2,000 GB

Standard

High

Environments with moderate load

120 TPS

Virtual or Physical server

16 cores (1)

128-256 GB (3)

3 disks:
OS: 50 GB
App/Logs: 100 GB
Data(2): 1-8 TB

Standard

High_20dv

Environments with medium to very high load

2,750 TPS (5)

Physical server

Needs sizing (5)

Needs sizing (5)

Needs sizing (5)

Standard

Federated ArchitectureEnvironments with high (Cell environment)

High load that requires several DPOD virtual servers

840 TPS (5)

Virtual servers

Needs sizing (5)

Needs sizing (5)

Needs sizing (5)

Standard

Federated ArchitectureEnvironments with very high (Cell environment)

High load that requires several DPOD physical servers

20,000 TPS (5)

Physical servers

Needs sizing (5)

Needs sizing (5)

Needs sizing (5)

(1) The hosting server (e.g. ESXi) CPU utilization should not exceed 80%. To ensure best indexing performance, the virtual machine configuration should be set to have reserved CPUs.

(2) Local SSD preferred - should be located on a data store separated from the other disks.

(3) To ensure best query performance, the virtual machine configuration should be set to have reserved memory.

(4) The TPS is the maximum total transactions load across all devices/domains connected to DPOD. 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).

...

(6) Using a single disk is only possible in the Non-Appliance Installation by specifying a special command line option. For more information, consult your DPOD SME that supports the POC/evaluation process.

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 RHEL built-in software 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.

...