From af4df125d0f04aecd0e9fdf939f0d619d0f73a6b Mon Sep 17 00:00:00 2001 From: Aolin Date: Tue, 4 Jul 2023 15:28:51 +0800 Subject: [PATCH] lightning: add a note for physical import mode Signed-off-by: Aolin --- migrate-large-mysql-to-tidb.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/migrate-large-mysql-to-tidb.md b/migrate-large-mysql-to-tidb.md index 972baabd29be2..b511e6eb607d5 100644 --- a/migrate-large-mysql-to-tidb.md +++ b/migrate-large-mysql-to-tidb.md @@ -9,7 +9,7 @@ When the data volume to be migrated is small, you can easily [use DM to migrate This document describes how to migrate large datasets from MySQL to TiDB. The whole migration has two processes: -1. *Full migration*. Use Dumpling and TiDB Lightning to perform the full migration. TiDB Lightning's **local backend** mode can import data at a speed of up to 500 GiB/h. +1. *Full migration*. Use Dumpling and TiDB Lightning to perform the full migration. TiDB Lightning's **local backend** mode can import data at a speed of up to 500 GiB/h. Note that this speed is affected by various factors such as hardware configuration, table schema, and the number of indexes. 2. *Incremental replication*. After the full migration is completed, you can replicate the incremental data using DM. ## Prerequisites