support the AVX2 instruction set. Ensure that cat /proc/cpuinfo | grep avx2 has output. To deploy TiFlash un- der the Linux ARM64 architecture, the CPU must support the ARMv8 instruction set architecture architecture. Ensure that cat /proc/cpuinfo | grep �→ 'crc32' | grep 'asimd' has output. By using the instruction set extensions, TiFlash’s vectorization engine can deliver better perfor- mance. 5.1.3.2 Production support installing JRE automatically. You need to install it on your own. For detailed installation instruction, see How to download and install prebuilt OpenJDK packages. If JRE 8 has already been installed

following CPU architectures are supported: • x86_64. Starting from TiDB v6.6.0, the x86-64-v2 instruction set is required. • ARM 64 5.1.2 Software recommendations 5.1.2.1 Control machine Software Version support the AVX2 instruction set. Ensure that cat /proc/cpuinfo | grep avx2 has output. To deploy TiFlash un- der the Linux ARM64 architecture, the CPU must support the ARMv8 instruction set architecture architecture. Ensure that cat /proc/cpuinfo | grep �→ 'crc32' | grep 'asimd' has output. By using the instruction set extensions, TiFlash’s vectorization engine can deliver better perfor- mance. 5.1.3.2 Production

following CPU architectures are supported: • x86_64. Starting from TiDB v6.6.0, the x86-64-v2 instruction set is required. 614 • ARM 64 5.1.2 Software recommendations 5.1.2.1 Control machine Software support the AVX2 instruction set. Ensure that cat /proc/cpuinfo | grep avx2 has output. To deploy TiFlash un- der the Linux ARM64 architecture, the CPU must support the ARMv8 instruction set architecture architecture. Ensure that cat /proc/cpuinfo | grep �→ 'crc32' | grep 'asimd' has output. By using the instruction set extensions, TiFlash’s vectorization engine can deliver better perfor- mance. 616 5.1.3.2 Production

following CPU architectures are supported: • x86_64. Starting from TiDB v6.6.0, the x86-64-v2 instruction set is required. • ARM 64 5.1.2 Software recommendations 5.1.2.1 Control machine 602 Software support the AVX2 instruction set. Ensure that cat /proc/cpuinfo | grep avx2 has output. To deploy TiFlash un- der the Linux ARM64 architecture, the CPU must support the ARMv8 instruction set architecture architecture. Ensure that cat /proc/cpuinfo | grep �→ 'crc32' | grep 'asimd' has output. By using the instruction set extensions, TiFlash’s vectorization engine can deliver better perfor- mance. 5.1.3.2 Production

following CPU architectures are supported: • x86_64. Starting from TiDB v6.6.0, the x86-64-v2 instruction set is required. • ARM 64 5.1.2 Software recommendations 5.1.2.1 Control machine Software Version support the AVX2 instruction set. Ensure that cat /proc/cpuinfo | grep avx2 has output. To deploy TiFlash un- der the Linux ARM64 architecture, the CPU must support the ARMv8 instruction set architecture architecture. Ensure that cat /proc/cpuinfo | grep �→ 'crc32' | grep 'asimd' has output. By using the instruction set extensions, TiFlash’s vectorization engine can deliver better perfor- mance. 5.1.3.2 Production

following CPU architectures are supported: • x86_64. Starting from TiDB v6.6.0, the x86-64-v2 instruction set is required. 630 • ARM 64 5.1.2 Software recommendations 5.1.2.1 Control machine Software support the AVX2 instruction set. Ensure that cat /proc/cpuinfo | grep avx2 has output. To deploy TiFlash un- der the Linux ARM64 architecture, the CPU must support the ARMv8 instruction set architecture architecture. Ensure that cat /proc/cpuinfo | grep �→ 'crc32' | grep 'asimd' has output. By using the instruction set extensions, TiFlash’s vectorization engine can deliver better perfor- mance. 632 5.1.3.2 Production

following CPU architectures are supported: • x86_64. Starting from TiDB v6.6.0, the x86-64-v2 instruction set is required. • ARM 64 5.1.2 Software recommendations 5.1.2.1 Control machine Software Version support the AVX2 instruction set. Ensure that cat /proc/cpuinfo | grep avx2 has output. To deploy TiFlash un- der the Linux ARM64 architecture, the CPU must support the ARMv8 instruction set architecture architecture. Ensure that cat /proc/cpuinfo | grep �→ 'crc32' | grep 'asimd' has output. By using the instruction set extensions, TiFlash’s vectorization engine can deliver better perfor- mance. 5.1.3.2 Production

following CPU architectures are supported: • x86_64. Starting from TiDB v6.6.0, the x86-64-v2 instruction set is required. • ARM 64 5.1.2 Software recommendations 5.1.2.1 Control machine Software Version v6.3.0, to deploy TiFlash under the Linux AMD64 archi- tecture, the CPU must support the AVX2 instruction set. Ensure that grep avx2 /proc/cpuinfo has output. To deploy TiFlash under the Linux ARM64 architecture architecture. Ensure that grep 'crc32' /proc/cpuinfo | �→ grep 'asimd' has output. By using the instruction set extensions, TiFlash’s vectorization engine can deliver better performance. 612 5.1.3.2 Production

following CPU architectures are supported: • x86_64. Starting from TiDB v6.6.0, the x86-64-v2 instruction set is required. • ARM 64 5.1.2 Software recommendations 5.1.2.1 Control machine Software Version v6.3.0, to deploy TiFlash under the Linux AMD64 archi- tecture, the CPU must support the AVX2 instruction set. Ensure that grep avx2 /proc/cpuinfo has output. To deploy TiFlash under the Linux ARM64 architecture architecture. Ensure that grep 'crc32' /proc/cpuinfo | �→ grep 'asimd' has output. By using the instruction set extensions, TiFlash’s vectorization engine can deliver better performance. 615 5.1.3.2 Production

support installing JRE automatically. You need to install it on your own. For detailed installation instruction, see How to download and install prebuilt OpenJDK packages. If JRE 8 has already been installed replicate the incremental data in cluster A to cluster B in real time. See the following steps for instruction. 5.5.2.1 Step 1. Enable TiDB Binlog Make sure that TiDB Binlog has been deployed and enabled 6 Can we share a link to a visualized snapshot? No, but you can share the snapshot file, with instruction on how to use the Visualizer to view it. If you truly need a world-readable URL, you may also try