Resource and hardware requirements
Make sure that you meet the following resource and hardware requirements for your configuration size before installing Obcerv.
T-shirt sizing for HA-enabled Copied
Large Copied
| Specification | Requirement |
|---|---|
| Obcerv entities | 250,000 |
| Messages per second limit | 100,000 |
| Messages per second target range | 50-100K |
| Operating system | Linux |
| CPU |
|
| RAM |
|
| Throughput |
|
| Disks (total estimate) | See Sample configuration for AWS EC2 handling 100k metrics/sec (large). |
Medium Copied
| Specification | Requirement |
|---|---|
| Obcerv entities | 125,000 |
| Messages per second limit | 50,000 |
| Messages per second target range | 10-50K |
| Operating system | Linux |
| CPU |
|
| RAM |
|
| Throughput |
|
| Disks (total estimate) | See Sample configuration for AWS EC2 handling 50k metrics/sec (medium). |
Small Copied
| Specification | Requirement |
|---|---|
| Obcerv entities | 25,000 |
| Messages per second limit | 10,000 |
| Messages per second target range | 0-10K |
| Operating system | Linux |
| CPU | 4 cores |
| RAM | 80 GiB memory |
| Throughput | 3000 IOPs / 125Mbps |
| Disks (total estimate) | See Sample configuration for AWS EC2 handling 10k metrics/sec (small). |
T-shirt sizing for Non-HA Copied
Small Copied
| Specification | Requirement |
|---|---|
| Obcerv entities | 25,000 |
| Messages per second limit | 10,000 |
| Messages per second target range | 0-10K |
| Operating system | Linux |
| CPU | 4 cores |
| RAM | 80 GiB memory |
| Throughput | 3000 IOPs / 125Mbps |
Micro Copied
| Specification | Requirement |
|---|---|
| Obcerv entities | 10,000 |
| Messages per second limit | 3,000 |
| Messages per second target range | 0-3K |
| Operating system | Linux |
| CPU | 16 cores |
| RAM | 64 GiB memory |
| Disks (total estimate) | 500 GB (SSD) See Sample configuration for AWS EC2 with ALB Ingress controller (micro). |
Storage considerations for embedded cluster installations Copied
-
PVCs are stored in the
/var/openebs/localdirectory, which does not reserve a specific amount of space upfront. The folder will initially use close to no space until files are actually added even when there is allocated storage space. Make sure that the total volume of your PVCs will fit within this directory. For example, if you have PVCs for Timescale (100 GB) and Kafka (100 GB), the directory needs to be at least 200 GB. -
The
/var/lib/k0s, which creates a Kubernetes cluster on the local machine, should have at least 100 GB and is not more than 80% full. -
The
/var/lib/embedded-clusterdirectory, which is used to store the installer, should have 40 GB or more of free space. -
The
/tmpdirectory, which serves as temporary space during installation, should be executable and have 20 GB or more of free space.
Relocate directories with bind mounts Copied
When installing on an embedded cluster with limited space, you can relocate directories by running:
sudo mount --bind /source/directory /target/directory
For example:
sudo mkdir -p /mnt/openebs /mnt/embedded-cluster /mnt/k0s /mnt/tmp
sudo mount --bind /mnt/openebs /var/openebs
sudo mount --bind /mnt/k0s /var/lib/k0s
sudo mount --bind /mnt/embedded-cluster /var/lib/embedded-cluster
sudo mount --bind /mnt/tmp /tmp