Cluster Sizing and Operations

이 페이지는 아직 영어로 제공되지 않습니다. 번역 작업 중입니다.
현재 번역 프로젝트에 대한 질문이나 피드백이 있으신 경우 언제든지 연락주시기 바랍니다.

CloudPrem is in Preview.

Overview

This document gives recommendations on dimensioning your CloudPrem cluster components, particularly indexers and searchers.

These are starting recommendations. Monitor your cluster's performance and resource utilization closely and adjust sizing as needed.

Performance: To index 5 MB/s of logs, CloudPrem needs approximately 1 vCPU and 2 GB of RAM.
Recommended Pod Sizes: We recommend deploying indexer pods with either:
- 2 vCPUs and 4 GB of RAM
- 4 vCPUs and 8 GB of RAM
- 8 vCPUs and 16 GB of RAM
Storage: Indexers require persistent storage (preferably SSDs, but local HDDs or remote EBS volumes can also be used) to store temporary data while constructing the index files.
- Minimum: 100 GB per pod
- Recommendation (for pods > 4 vCPUs): 200 GB per pod
Example Calculation: To index 1 TB per day (~11.6 MB/s):
- Required vCPUs: (11.6 MB/s / 5 MB/s/vCPU) ≈ 2.3 vCPUs
- Rounding up, you might start with one indexer pod configured with 3 vCPUs and 6 GB RAM, requiring a 100 GB EBS volume. (Adjust this configuration based on observed performance and redundancy needs.)

Performance: Search performance depends heavily on the workload (query complexity, concurrency, data scanned).
Rule of Thumb: A general starting point is to provision roughly double the total number of vCPUs allocated to Indexers.
Memory: We recommend 4 GB of RAM per searcher vCPU. Provision more RAM if you expect many concurrent aggregation requests.

The following components are typically lightweight:

Instance Size: For most use cases, a PostgreSQL instance with 1 vCPU and 4 GB of RAM is sufficient
AWS RDS Recommendation: If using AWS RDS, the t4g.medium instance type is a suitable starting point
High Availability: Enable Multi-AZ deployment with one standby replica for high availability