From 5b5d1d7b89f41d492ace29f80aae60aadb018d48 Mon Sep 17 00:00:00 2001 From: houfaxin Date: Fri, 8 Nov 2024 09:16:56 +0800 Subject: [PATCH 1/7] Update hardware-and-software-requirements.md --- hardware-and-software-requirements.md | 1 + 1 file changed, 1 insertion(+) diff --git a/hardware-and-software-requirements.md b/hardware-and-software-requirements.md index bc369954c1c75..5709e3029f30d 100644 --- a/hardware-and-software-requirements.md +++ b/hardware-and-software-requirements.md @@ -184,6 +184,7 @@ Before you deploy TiFlash, note the following items: - TiFlash can be [deployed on multiple disks](/tiflash/tiflash-configuration.md#multi-disk-deployment). - It is recommended to use a high-performance SSD as the first disk of the TiFlash data directory to buffer the real-time replication of TiKV data. The performance of this disk should not be lower than that of TiKV, such as PCIe SSD. The disk capacity should be no less than 10% of the total capacity; otherwise, it might become the bottleneck of this node. You can deploy ordinary SSDs for other disks, but note that a better PCIe SSD brings better performance. - It is recommended to deploy TiFlash on different nodes from TiKV. If you must deploy TiFlash and TiKV on the same node, increase the number of CPU cores and memory, and try to deploy TiFlash and TiKV on different disks to avoid interfering each other. +- If you deploy your TiDB cluster on a cloud provider, such as AWS, Google Cloud, or Azure, TiKV nodes must use cloud disks. Data on local disks will be lost if the instance crashes in the cloud environment. - The total capacity of the TiFlash disks is calculated in this way: `the data volume of the entire TiKV cluster to be replicated / the number of TiKV replicas * the number of TiFlash replicas`. For example, if the overall planned capacity of TiKV is 1 TB, the number of TiKV replicas is 3, and the number of TiFlash replicas is 2, then the recommended total capacity of TiFlash is `1024 GB / 3 * 2`. You can replicate only the data of some tables. In such case, determine the TiFlash capacity according to the data volume of the tables to be replicated. Before you deploy TiCDC, note that it is recommended to deploy TiCDC on PCIe SSD disks larger than 500 GB. From e5c3bcf336bc123852384ba3e58668348c90b9e9 Mon Sep 17 00:00:00 2001 From: houfaxin Date: Fri, 8 Nov 2024 09:25:09 +0800 Subject: [PATCH 2/7] Update hardware-and-software-requirements.md --- hardware-and-software-requirements.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/hardware-and-software-requirements.md b/hardware-and-software-requirements.md index 5709e3029f30d..d9eb929927889 100644 --- a/hardware-and-software-requirements.md +++ b/hardware-and-software-requirements.md @@ -178,13 +178,13 @@ You can deploy and run TiDB on the 64-bit generic hardware server platform in th > - In the production environment, the TiDB and PD instances can be deployed on the same server. If you have a higher requirement for performance and reliability, try to deploy them separately. > - It is strongly recommended to configure TiDB, TiKV, and TiFlash with at least 8 CPU cores each in the production environment. To get better performance, a higher configuration is recommended. > - It is recommended to keep the size of TiKV hard disk within 4 TB if you are using PCIe SSDs or within 1.5 TB if you are using regular SSDs. +> - If you deploy your TiDB cluster on a cloud provider, such as AWS, Google Cloud, or Azure, TiKV nodes must use cloud disks. Data on local disks will be lost if the instance crashes in the cloud environment. Before you deploy TiFlash, note the following items: - TiFlash can be [deployed on multiple disks](/tiflash/tiflash-configuration.md#multi-disk-deployment). - It is recommended to use a high-performance SSD as the first disk of the TiFlash data directory to buffer the real-time replication of TiKV data. The performance of this disk should not be lower than that of TiKV, such as PCIe SSD. The disk capacity should be no less than 10% of the total capacity; otherwise, it might become the bottleneck of this node. You can deploy ordinary SSDs for other disks, but note that a better PCIe SSD brings better performance. - It is recommended to deploy TiFlash on different nodes from TiKV. If you must deploy TiFlash and TiKV on the same node, increase the number of CPU cores and memory, and try to deploy TiFlash and TiKV on different disks to avoid interfering each other. -- If you deploy your TiDB cluster on a cloud provider, such as AWS, Google Cloud, or Azure, TiKV nodes must use cloud disks. Data on local disks will be lost if the instance crashes in the cloud environment. - The total capacity of the TiFlash disks is calculated in this way: `the data volume of the entire TiKV cluster to be replicated / the number of TiKV replicas * the number of TiFlash replicas`. For example, if the overall planned capacity of TiKV is 1 TB, the number of TiKV replicas is 3, and the number of TiFlash replicas is 2, then the recommended total capacity of TiFlash is `1024 GB / 3 * 2`. You can replicate only the data of some tables. In such case, determine the TiFlash capacity according to the data volume of the tables to be replicated. Before you deploy TiCDC, note that it is recommended to deploy TiCDC on PCIe SSD disks larger than 500 GB. From 84cdbd7b29cc29d54d2d82b7771ce8188a8ca142 Mon Sep 17 00:00:00 2001 From: xixirangrang Date: Fri, 8 Nov 2024 09:33:32 +0800 Subject: [PATCH 3/7] Update hardware-and-software-requirements.md --- hardware-and-software-requirements.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/hardware-and-software-requirements.md b/hardware-and-software-requirements.md index d9eb929927889..df6d8151bee01 100644 --- a/hardware-and-software-requirements.md +++ b/hardware-and-software-requirements.md @@ -178,7 +178,7 @@ You can deploy and run TiDB on the 64-bit generic hardware server platform in th > - In the production environment, the TiDB and PD instances can be deployed on the same server. If you have a higher requirement for performance and reliability, try to deploy them separately. > - It is strongly recommended to configure TiDB, TiKV, and TiFlash with at least 8 CPU cores each in the production environment. To get better performance, a higher configuration is recommended. > - It is recommended to keep the size of TiKV hard disk within 4 TB if you are using PCIe SSDs or within 1.5 TB if you are using regular SSDs. -> - If you deploy your TiDB cluster on a cloud provider, such as AWS, Google Cloud, or Azure, TiKV nodes must use cloud disks. Data on local disks will be lost if the instance crashes in the cloud environment. +> - If you deploy your TiKV on a cloud provider, such as AWS, Google Cloud, or Azure, TiKV nodes must use cloud disks. Data on local disks will be lost if the instance crashes in the cloud environment. Before you deploy TiFlash, note the following items: From db827b13858f563e2bdf430b6bba54b085af021a Mon Sep 17 00:00:00 2001 From: xixirangrang Date: Fri, 8 Nov 2024 10:39:22 +0800 Subject: [PATCH 4/7] Update hardware-and-software-requirements.md --- hardware-and-software-requirements.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/hardware-and-software-requirements.md b/hardware-and-software-requirements.md index df6d8151bee01..c96107a48148e 100644 --- a/hardware-and-software-requirements.md +++ b/hardware-and-software-requirements.md @@ -178,7 +178,7 @@ You can deploy and run TiDB on the 64-bit generic hardware server platform in th > - In the production environment, the TiDB and PD instances can be deployed on the same server. If you have a higher requirement for performance and reliability, try to deploy them separately. > - It is strongly recommended to configure TiDB, TiKV, and TiFlash with at least 8 CPU cores each in the production environment. To get better performance, a higher configuration is recommended. > - It is recommended to keep the size of TiKV hard disk within 4 TB if you are using PCIe SSDs or within 1.5 TB if you are using regular SSDs. -> - If you deploy your TiKV on a cloud provider, such as AWS, Google Cloud, or Azure, TiKV nodes must use cloud disks. Data on local disks will be lost if the instance crashes in the cloud environment. +> - If you deploy your TiKV on a cloud provider, such as AWS, Google Cloud, or Azure, it is recommended to use cloud disks for TiKV nodes. Data on local disks will be lost if the instance crashes in the cloud environment. Before you deploy TiFlash, note the following items: From 1759de8682e75f7a00005bae5e0cc83fd0bf0fa4 Mon Sep 17 00:00:00 2001 From: xixirangrang Date: Fri, 8 Nov 2024 10:40:13 +0800 Subject: [PATCH 5/7] Update hardware-and-software-requirements.md --- hardware-and-software-requirements.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/hardware-and-software-requirements.md b/hardware-and-software-requirements.md index c96107a48148e..725b226ef8e03 100644 --- a/hardware-and-software-requirements.md +++ b/hardware-and-software-requirements.md @@ -178,7 +178,7 @@ You can deploy and run TiDB on the 64-bit generic hardware server platform in th > - In the production environment, the TiDB and PD instances can be deployed on the same server. If you have a higher requirement for performance and reliability, try to deploy them separately. > - It is strongly recommended to configure TiDB, TiKV, and TiFlash with at least 8 CPU cores each in the production environment. To get better performance, a higher configuration is recommended. > - It is recommended to keep the size of TiKV hard disk within 4 TB if you are using PCIe SSDs or within 1.5 TB if you are using regular SSDs. -> - If you deploy your TiKV on a cloud provider, such as AWS, Google Cloud, or Azure, it is recommended to use cloud disks for TiKV nodes. Data on local disks will be lost if the instance crashes in the cloud environment. +> - If you deploy your TiKV on a cloud provider, such as AWS, Google Cloud, or Azure, it is recommended to use cloud disks for TiKV nodes. Data on local disks might be lost if the instance crashes in the cloud environment. Before you deploy TiFlash, note the following items: From ba636c7119bbcb77e59b5aae3342f7cb5aadb8d1 Mon Sep 17 00:00:00 2001 From: xixirangrang Date: Fri, 8 Nov 2024 10:41:02 +0800 Subject: [PATCH 6/7] Update hardware-and-software-requirements.md --- hardware-and-software-requirements.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/hardware-and-software-requirements.md b/hardware-and-software-requirements.md index 725b226ef8e03..a2511c77e713c 100644 --- a/hardware-and-software-requirements.md +++ b/hardware-and-software-requirements.md @@ -178,7 +178,7 @@ You can deploy and run TiDB on the 64-bit generic hardware server platform in th > - In the production environment, the TiDB and PD instances can be deployed on the same server. If you have a higher requirement for performance and reliability, try to deploy them separately. > - It is strongly recommended to configure TiDB, TiKV, and TiFlash with at least 8 CPU cores each in the production environment. To get better performance, a higher configuration is recommended. > - It is recommended to keep the size of TiKV hard disk within 4 TB if you are using PCIe SSDs or within 1.5 TB if you are using regular SSDs. -> - If you deploy your TiKV on a cloud provider, such as AWS, Google Cloud, or Azure, it is recommended to use cloud disks for TiKV nodes. Data on local disks might be lost if the instance crashes in the cloud environment. +> - If you deploy TiKV on a cloud provider, such as AWS, Google Cloud, or Azure, it is recommended to use cloud disks for TiKV nodes. Data on local disks might be lost if the instance crashes in the cloud environment. Before you deploy TiFlash, note the following items: From c17731bef1695aa26cbb94663a5bd207ccd66c3d Mon Sep 17 00:00:00 2001 From: xixirangrang Date: Fri, 15 Nov 2024 10:41:42 +0800 Subject: [PATCH 7/7] Update hardware-and-software-requirements.md Co-authored-by: Grace Cai --- hardware-and-software-requirements.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/hardware-and-software-requirements.md b/hardware-and-software-requirements.md index a2511c77e713c..1442ed06ffdda 100644 --- a/hardware-and-software-requirements.md +++ b/hardware-and-software-requirements.md @@ -178,7 +178,7 @@ You can deploy and run TiDB on the 64-bit generic hardware server platform in th > - In the production environment, the TiDB and PD instances can be deployed on the same server. If you have a higher requirement for performance and reliability, try to deploy them separately. > - It is strongly recommended to configure TiDB, TiKV, and TiFlash with at least 8 CPU cores each in the production environment. To get better performance, a higher configuration is recommended. > - It is recommended to keep the size of TiKV hard disk within 4 TB if you are using PCIe SSDs or within 1.5 TB if you are using regular SSDs. -> - If you deploy TiKV on a cloud provider, such as AWS, Google Cloud, or Azure, it is recommended to use cloud disks for TiKV nodes. Data on local disks might be lost if the instance crashes in the cloud environment. +> - If you deploy TiKV on a cloud provider, such as AWS, Google Cloud, or Azure, it is recommended to use cloud disks for TiKV nodes. Data on local disks might be lost if the TiKV instance crashes in the cloud environment. Before you deploy TiFlash, note the following items: