diff --git a/TOC.md b/TOC.md
index f7ddc23396bfe..dbad43bbd7458 100644
--- a/TOC.md
+++ b/TOC.md
@@ -317,6 +317,7 @@
     - [Scale TiFlash](/reference/tiflash/scale.md)
     - [Upgrade TiFlash Nodes](/reference/tiflash/upgrade.md)
     - [Configure TiFlash](/reference/tiflash/configuration.md)
+    - [Tune TiFlash Performance](/reference/tiflash/tune-performance.md)
   + TiDB Binlog
     - [Overview](/reference/tidb-binlog/overview.md)
     - [Deploy](/reference/tidb-binlog/deploy.md)
diff --git a/reference/tiflash/tune-performance.md b/reference/tiflash/tune-performance.md
new file mode 100644
index 0000000000000..efda5c98831e9
--- /dev/null
+++ b/reference/tiflash/tune-performance.md
@@ -0,0 +1,31 @@
+---
+title: Tune TiFlash Performance
+summary: Learn how to tune the performance of TiFlash.
+category: reference
+---
+
+# Tune TiFlash Performance
+
+This document introduces how to tune the performance of TiFlash, including planning machine resources and tuning TiDB parameters.
+
+## Plan resources
+
+If you want to save machine resources and have no requirement on isolation, you can use the method that combines the deployment of both TiKV and TiFlash. It is recommended that you save enough resources for TiKV and TiFlash respectively, and do not share disks.
+
+## Tune TiDB parameters
+
+1. For the TiDB node dedicated to OLAP/TiFlash, it is recommended that you increase the value of the [`tidb_distsql_scan_concurrency`](/reference/configuration/tidb-server/tidb-specific-variables.md#tidb_distsql_scan_concurrency) configuration item for this node to `80`:
+
+    {{< copyable "sql" >}}
+
+    ```sql
+    set @@tidb_distsql_scan_concurrency = 80;
+    ```
+
+2. Enable the optimization for TiDB Operator such as the aggregate pushdown of `JOIN` or `UNION`:
+
+    {{< copyable "sql" >}}
+
+    ```sql
+    set @@tidb_opt_agg_push_down = 1;
+    ```