Database Resources
About 3 min
Database Resources
1. CPU and Memory
The following are minimum resource recommendations for sampling frequencies of up to 1 Hz. The table uses a CPU-to-memory ratio of 1:4; actual resource requirements also depend on query load, data types, and write frequency.
| Number of active timeseries | CPU | Memory | Number of nodes | ||
|---|---|---|---|---|---|
| Standalone | Dual-Active | Distributed | |||
| Within 100,000 | 1-2 cores | 2-8 GB | 1 | 2 | 3 |
| Within 300,000 | 2-4 cores | 8-16 GB | 1 | 2 | 3 |
| Within 500,000 | 4-8 cores | 16-32 GB | 1 | 2 | 3 |
| Within 1,000,000 | 8-16 cores | 32-64 GB | 1 | 2 | 3 |
| Within 2,000,000 | 16-32 cores | 64-128 GB | 1 | 2 | 3 |
| Within 10,000,000 | 48 cores | 192 GB | 1 | 2 | Please contact Timecho Business for consultation |
| Over 10,000,000 | Please contact Timecho Business for consultation | ||||
Notes:
- Supported CPU models: Kunpeng, Phytium, Sunway, Hygon, Zhaoxin, Loongson
- Memory settings can be adjusted flexibly in the datanode-env file. For details and configuration guidelines, see datanode-env.
- To configure AI model inference, refer to the TimechoAI User Manual.
2. Storage (Disk)
2.1 Storage space
Calculation Formula:
Storage Space = Number of Measurement Points * Sampling Frequency (Hz) * Size of Each Data Point (Bytes, see the table below) * Storage Duration * Replication Factor / Compression RatioData Point Size Calculation Table:
| Data Type | Timestamp (Bytes) | Value (Bytes) | Total Data Point Size (Bytes) |
|---|---|---|---|
| Boolean | 8 | 1 | 9 |
| INT32 / FLOAT (Single Precision) | 8 | 4 | 12 |
| INT64 / DOUBLE (Double Precision) | 8 | 8 | 16 |
| TEXT (String) | 8 | Average = a | 8+a |
- Scenario: 1,000 devices, 100 measurement points per device, i.e. 100,000 sequences in total. Data type is INT32. Sampling frequency is 1Hz (once per second). Storage duration is 1 year. Replication factor is 3.
- Full Calculation:
1,000 devices * 100 measurement points * 12 bytes per data point * 86,400 seconds per day * 365 days per year * 3 replicas / 10 compression ratio = 11 TB - Simplified Calculation:
1,000 * 100 * 12 * 86,400 * 365 * 3 / 10 = 11 TB
2.2 Storage Configuration
- For systems with > 10 million measurement points or high query loads, SSD is recommended.
3. Network (NIC)
When the write throughput does not exceed 10 million points per second, a gigabit network card is required. When the write throughput exceeds 10 million points per second, a 10-gigabit network card is required.
| Write Throughput (Data Points/Second) | NIC Speed |
|---|---|
| < 10 million | 1 Gbps (Gigabit) |
| ≥ 10 million | 10 Gbps (10 Gigabit) |
4. Additional Notes
- IoTDB supports second-level cluster scaling . Data migration is not required when adding new nodes, so there is no need to worry about limited cluster capacity based on current data estimates. You can add new nodes to the cluster when scaling is needed in the future.