Analytical Processing (OLAP) workloads may be supported by an HTAP database, which offers speed and simplicity. TiDB is using Storage engines, Data consistency, Data isolation, and the MPP computing engine

special character into an identifier character, precede it with a backslash \. db\.with\.dots.* For simplicity and future compatibility, the following sequences are prohibited: • \ at the end of the line after the task. • mydumpers.threads can be replaced with the mydumper-thread config- uration item for simplicity. • If rows is set，DM ignores the value of chunk-filesize. 11.9.6.1.2 Full data import loaders the task. • loaders.pool-size can be replaced with the loader-thread configura- tion item for simplicity. 11.9.6.1.3 Incremental data replication syncers is the configuration item related to incremental

the task. • mydumpers.threads can be replaced with the mydumper-thread config- uration item for simplicity. • If rows is set, DM ignores the value of chunk-filesize. Full data import loaders is the configuration the task. • loaders.pool-size can be replaced with the loader-thread configura- tion item for simplicity. Incremental data replication syncers is the configuration item related to incremental data replication the task. • syncers.worker-count can be replaced with the syncer-thread config- uration item for simplicity. • You can change the values of worker-count and batch according to the actual scenario. For example

control limits concurrent on-the-fly requests by committer-concurrency (default value is 128). For simplicity, the flow control can be treated as an amplification of request latency (round). The tidb_tik the task. • mydumpers.threads can be replaced with the mydumper-thread config- uration item for simplicity. • If rows is set, DM ignores the value of chunk-filesize. Full data import loaders is the configuration the task. • loaders.pool-size can be replaced with the loader-thread configura- tion item for simplicity. Incremental data replication syncers is the configuration item related to incremental data replication

control limits concurrent on-the-fly requests by committer-concurrency (default value is 128). For simplicity, the flow control can be treated as an amplification of request latency (round). The tidb_tik the task. • mydumpers.threads can be replaced with the mydumper-thread config- uration item for simplicity. • If rows is set, DM ignores the value of chunk-filesize. Full data import loaders is the configuration the task. • loaders.pool-size can be replaced with the loader-thread configura- tion item for simplicity. Incremental data replication syncers is the configuration item related to incremental data replication

control limits concurrent on-the-fly requests by committer-concurrency (default value is 128). For simplicity, the flow control can be treated as an amplification of request latency (round). The tidb_tik the task. • mydumpers.threads can be replaced with the mydumper-thread config- uration item for simplicity. • If rows is set, DM ignores the value of chunk-filesize. Full data import loaders is the configuration the task. • loaders.pool-size can be replaced with the loader-thread configura- tion item for simplicity. Incremental data replication syncers is the configuration item related to incremental data replication

control limits concurrent on-the-fly requests by committer-concurrency (default value is 128). For simplicity, the flow control can be treated as an amplification of request latency (round). The tidb_tik the task. • mydumpers.threads can be replaced with the mydumper-thread config- uration item for simplicity. • If rows is set, DM ignores the value of chunk-filesize. Full data import loaders is the configuration the task. • loaders.pool-size can be replaced with the loader-thread configura- tion item for simplicity. Incremental data replication syncers is the configuration item related to incremental data replication

control limits concurrent on-the-fly requests by committer-concurrency (default value is 128). For simplicity, the flow control can be treated as an amplification of request latency (round). The tidb_tik the task. • mydumpers.threads can be replaced with the mydumper-thread config- uration item for simplicity. • If rows is set, DM ignores the value of chunk-filesize. Full data import loaders is the configuration the task. • loaders.pool-size can be replaced with the loader-thread configura- tion item for simplicity. Incremental data replication syncers is the configuration item related to incremental data replication

control limits concurrent on-the-fly requests by committer-concurrency (default value is 128). For simplicity, the flow control can be treated as an amplification of request latency (round). The tidb_tik the task. • mydumpers.threads can be replaced with the mydumper-thread config- uration item for simplicity. • If rows is set, DM ignores the value of chunk-filesize. Full data import loaders is the configuration the task. • loaders.pool-size can be replaced with the loader-thread configura- tion item for simplicity. Incremental data replication syncers is the configuration item related to incremental data replication

control limits concurrent on-the-fly requests by committer-concurrency (default value is 128). For simplicity, the flow control can be treated as an amplification of request latency (round). The tidb_tik the task. • mydumpers.threads can be replaced with the mydumper-thread config- uration item for simplicity. • If rows is set, DM ignores the value of chunk-filesize. Full data import loaders is the configuration the task. • loaders.pool-size can be replaced with the loader-thread configura- tion item for simplicity. Incremental data replication syncers is the configuration item related to incremental data replication