Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

update hardware requirement for disaggregated tiflash #16642

Merged
merged 7 commits into from
Mar 12, 2024
Merged
Changes from 4 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
30 changes: 30 additions & 0 deletions hardware-and-software-requirements.md
Original file line number Diff line number Diff line change
Expand Up @@ -267,3 +267,33 @@ As an open-source distributed SQL database, TiDB requires the following network
## Web browser requirements

TiDB relies on [Grafana](https://grafana.com/) to provide visualization of database metrics. A recent version of Microsoft Edge, Safari, Chrome or Firefox with Javascript enabled is sufficient.

## Hardware and Software Requirements for TiFlash Disaggregated Storage and Compute Architecture

All the descriptions above are for the coupled TiFlash architecture. Starting from v7.0.0, TiFlash introduces support for the [disaggregated of storage and compute](/tiflash/tiflash-disaggregated-and-s3.md) architecture. In this architecture, TiFlash is divided into storage nodes and compute nodes. The corresponding hardware and software requirements are as follows:

1. Software: The operating system and platform requirements are same with the coupled storage and compute architecture.
2. Network Ports: Network port requirements are same with the coupled storage and compute mode.
3. Disk Space Requirements:
1. Storage Nodes: Same with the coupled storage and compute mode, but an S3-compatible object storage is required.
2. Compute Nodes: Recommended 100GB. The storage on compute nodes is mainly used to cache data read from storage nodes to accelerate performance. Therefore, it is normal to see the cache on compute nodes being fully utilized.
4. CPU and Other Memory Requirements - Refer to the Next Section

### Development and Testing Environment

| **Component** | **CPU** | **Memory** | **Local Storage** | **Network** | **Instance Quantity (Minimum Requirement)** |
| --- | --- | --- | --- | --- | --- |
| TiFlash Storage Node | 16 cores+ | 32 GB+ | SSD, 200 GB+ | Gigabit Ethernet | 1 |
| TiFlash Compute Node | 16 cores+ | 32 GB+ | SSD, 100 GB+ | Gigabit Ethernet | 0 |

### Production Environment

| **Component** | **CPU** | **Memory** | **Disk Type** | **Network** | **Instance Quantity (Minimum Requirement)** |
| --- | --- | --- | --- | --- | --- |
| TiFlash Storage Node | 32 cores+ | 64 GB+ | 1 or more SSDs | 10 Gigabit Ethernet (2 recommended) | 1 |
| TiFlash Compute Node | 32 cores+ | 64 GB+ | 1 or more SSDs | 10 Gigabit Ethernet (2 recommended) | 0 |

> **Note:**
>
> - TiFlash Compute Nodes can be quickly scaled in or out using deployment tools such as TiUP, with a scaling range of [0, inf+].

guo-shaoge marked this conversation as resolved.
Show resolved Hide resolved
Loading