The Clone Plugin clone_autotune_concurrency  is disabled,  clone_max_concurrency  defines the number of threads spawned for a remote cloning operation. A minimum data transfer rate of 1 mebibyte (MiB) per thread is recommended for remote cloning operations. The data transfer rate for a remote cloning operation is controlled by the clone_max_data_bandwidth  variable. • clone_max_data_bandwidth Command-Line Format --clone-max-data-bandwidth Introduced 8.0.17 System Variable clone_max_data_bandwidth Scope Global Dynamic Yes SET_VAR  Hint Applies No Type Integer Default Value 0 Minimum Value 0 Maximum Value 1048576 Unit miB/second Defines the maximum data transfer rate in mebibytes (MiB) per second for a remote cloning operation. This variable helps manage the performance impact of a cloning operation. A limit should be set only when donor disk I/O bandwidth is saturated, affecting performance. A value of 0 means “unlimited” , which permits cloning operations to run at the highest possible data transfer rate. This setting is only applicable to the recipient MySQL server instance. The minimum data transfer rate is 1 MiB per second, per thread. For example, if there are 8 threads, the minimum transfer rate is 8 MiB per second. The  clone_max_concurrency  variable controls the maximum number threads spawned for a remote cloning operation. The requested data transfer rate specified by  clone_max_data_bandwidth  may differ from the actual data transfer rate reported by the  DATA_SPEED  column in the performance_schema.clone_progress  table. If your cloning operation is not achieving the desired data transfer rate and you have available bandwidth, check I/O usage on the recipient and donor. If there is underutilized bandwidth, I/O is the next mostly likely bottleneck. • clone_max_network_bandwidth Command-Line Format --clone-max-network-bandwidth Introduced 8.0.17 System Variable clone_max_network_bandwidth Scope Global Dynamic Yes SET_VAR  Hint Applies No Type Integer Default Value 0 Minimum Value 0 1132