From 11c4a25240b63b441ef4b1ba7e5341e416a42c42 Mon Sep 17 00:00:00 2001 From: Ti Chi Robot Date: Wed, 18 Jan 2023 20:41:50 +0800 Subject: [PATCH] Update tiflash-overview.md (#10635) (#12143) --- tiflash/tiflash-overview.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/tiflash/tiflash-overview.md b/tiflash/tiflash-overview.md index 3115deca6671..db4e4f644384 100644 --- a/tiflash/tiflash-overview.md +++ b/tiflash/tiflash-overview.md @@ -25,6 +25,8 @@ TiFlash provides the columnar storage, with a layer of coprocessors efficiently TiFlash conducts real-time replication of data in the TiKV nodes at a low cost that does not block writes in TiKV. Meanwhile, it provides the same read consistency as in TiKV and ensures that the latest data is read. The Region replica in TiFlash is logically identical to those in TiKV, and is split and merged along with the Leader replica in TiKV at the same time. +To deploy TiFlash under the Linux AMD64 architecture, the CPU must support AVX2 instruction sets. Use `cat /proc/cpuinfo | grep avx2` to confirm that there is output. By using such CPU instruction sets, TiFlash's vectorization engine can deliver better performance. + TiFlash is compatible with both TiDB and TiSpark, which enables you to freely choose between these two computing engines. It is recommended that you deploy TiFlash in different nodes from TiKV to ensure workload isolation. It is also acceptable to deploy TiFlash and TiKV in the same node if no business isolation is required.