diff --git a/markdown-pages/en/tidb/master/TOC.md b/markdown-pages/en/tidb/master/TOC.md
index 438109b..36716ca 100644
--- a/markdown-pages/en/tidb/master/TOC.md
+++ b/markdown-pages/en/tidb/master/TOC.md
@@ -4,15 +4,15 @@
 - [Docs Home](https://docs.pingcap.com/)
 - About TiDB Self-Managed
   - [What is TiDB Self-Managed](/overview.md)
-  - [TiDB 8.4 Release Notes](/releases/release-8.4.0.md)
+  - [TiDB 8.3 Release Notes](/releases/release-8.3.0.md)
   - [Features](/basic-features.md)
   - [MySQL Compatibility](/mysql-compatibility.md)
   - [TiDB Limitations](/tidb-limitations.md)
   - [Credits](/credits.md)
   - [Roadmap](/tidb-roadmap.md)
-- Get Started
-  - [Quick Start with TiDB](/quick-start-with-tidb.md)
-  - [Quick Start with HTAP](/quick-start-with-htap.md)
+- Quick Start
+  - [Try Out TiDB](/quick-start-with-tidb.md)
+  - [Try Out HTAP](/quick-start-with-htap.md)
   - [Learn TiDB SQL](/basic-sql-operations.md)
   - [Learn HTAP](/explore-htap.md)
   - [Import Example Database](/import-example-data.md)
@@ -81,24 +81,6 @@
       - [Follower Read](/develop/dev-guide-use-follower-read.md)
       - [Stale Read](/develop/dev-guide-use-stale-read.md)
     - [HTAP Queries](/develop/dev-guide-hybrid-oltp-and-olap-queries.md)
-  - Vector Search
-    - [Overview](/vector-search-overview.md)
-    - Get Started
-      - [Get Started with SQL](/vector-search-get-started-using-sql.md)
-      - [Get Started with Python](/vector-search-get-started-using-python.md)
-    - Integrations
-      - [Overview](/vector-search-integration-overview.md)
-      - AI Frameworks
-        - [LlamaIndex](/vector-search-integrate-with-llamaindex.md)
-        - [Langchain](/vector-search-integrate-with-langchain.md)
-      - Embedding Models/Services
-        - [Jina AI](/vector-search-integrate-with-jinaai-embedding.md)
-      - ORM Libraries
-        - [SQLAlchemy](/vector-search-integrate-with-sqlalchemy.md)
-        - [peewee](/vector-search-integrate-with-peewee.md)
-        - [Django](/vector-search-integrate-with-django-orm.md)
-    - [Improve Performance](/vector-search-improve-performance.md)
-    - [Limitations](/vector-search-limitations.md)
   - Transaction
     - [Overview](/develop/dev-guide-transaction-overview.md)
     - [Optimistic and Pessimistic Transactions](/develop/dev-guide-optimistic-and-pessimistic-transaction.md)
@@ -140,8 +122,9 @@
     - [TiSpark Topology](/tispark-deployment-topology.md)
     - [Cross-DC Topology](/geo-distributed-deployment-topology.md)
     - [Hybrid Topology](/hybrid-deployment-topology.md)
-  - [Deploy Using TiUP](/production-deployment-using-tiup.md)
-  - [Deploy on Kubernetes](/tidb-in-kubernetes.md)
+  - Install and Start
+    - [Use TiUP](/production-deployment-using-tiup.md)
+    - [Deploy on Kubernetes](/tidb-in-kubernetes.md)
   - [Verify Cluster Status](/post-installation-check.md)
   - Test Cluster Performance
     - [Test TiDB Using Sysbench](/benchmark/benchmark-tidb-using-sysbench.md)
@@ -157,7 +140,6 @@
     - [Migrate Large Datasets from MySQL](/migrate-large-mysql-to-tidb.md)
     - [Migrate and Merge MySQL Shards of Small Datasets](/migrate-small-mysql-shards-to-tidb.md)
     - [Migrate and Merge MySQL Shards of Large Datasets](/migrate-large-mysql-shards-to-tidb.md)
-    - [Migrate from Vitess](/migrate-from-vitess.md)
     - [Migrate from MariaDB](/migrate-from-mariadb.md)
     - [Migrate from CSV Files](/migrate-from-csv-files-to-tidb.md)
     - [Migrate from SQL Files](/migrate-from-sql-files-to-tidb.md)
@@ -169,61 +151,12 @@
     - [Migrate to a Downstream Table with More Columns](/migrate-with-more-columns-downstream.md)
     - [Filter Binlog Events](/filter-binlog-event.md)
     - [Filter DML Events Using SQL Expressions](/filter-dml-event.md)
-- Stream Data
-  - [TiCDC Overview](/ticdc/ticdc-overview.md)
-  - [Deploy and Maintain](/ticdc/deploy-ticdc.md)
-  - Changefeed
-    - [Overview](/ticdc/ticdc-changefeed-overview.md)
-    - Create Changefeeds
-      - [Replicate Data to MySQL-compatible Databases](/ticdc/ticdc-sink-to-mysql.md)
-      - [Replicate Data to Kafka](/ticdc/ticdc-sink-to-kafka.md)
-      - [Replicate Data to Pulsar](/ticdc/ticdc-sink-to-pulsar.md)
-      - [Replicate Data to Storage Services](/ticdc/ticdc-sink-to-cloud-storage.md)
-    - [Manage Changefeeds](/ticdc/ticdc-manage-changefeed.md)
-    - [Log Filter](/ticdc/ticdc-filter.md)
-    - [DDL Replication](/ticdc/ticdc-ddl.md)
-    - [Bidirectional Replication](/ticdc/ticdc-bidirectional-replication.md)
-  - Monitor and Alert
-    - [Monitoring Metrics Summary](/ticdc/ticdc-summary-monitor.md)
-    - [Monitoring Metrics Details](/ticdc/monitor-ticdc.md)
-    - [Alert Rules](/ticdc/ticdc-alert-rules.md)
+- Integrate
+  - [Overview](/integration-overview.md)
   - Integration Scenarios
-    - [Overview](/integration-overview.md)
     - [Integrate with Confluent and Snowflake](/ticdc/integrate-confluent-using-ticdc.md)
     - [Integrate with Apache Kafka and Apache Flink](/replicate-data-to-kafka.md)
-  - Reference
-    - [TiCDC Architecture](/ticdc/ticdc-architecture.md)
-    - [TiCDC Server Configurations](/ticdc/ticdc-server-config.md)
-    - [TiCDC Changefeed Configurations](/ticdc/ticdc-changefeed-config.md)
-    - [TiCDC Client Authentication](/ticdc/ticdc-client-authentication.md)
-    - [Data Integrity Validation for Single-Row Data](/ticdc/ticdc-integrity-check.md)
-    - [Data Consistency Validation for Upstream and Downstream TiDB Clusters](/ticdc/ticdc-upstream-downstream-check.md)
-    - [TiCDC Behavior in Splitting UPDATE Events](/ticdc/ticdc-split-update-behavior.md)
-    - Output Protocols
-      - [TiCDC Avro Protocol](/ticdc/ticdc-avro-protocol.md)
-      - [TiCDC Canal-JSON Protocol](/ticdc/ticdc-canal-json.md)
-      - [TiCDC CSV Protocol](/ticdc/ticdc-csv.md)
-      - [TiCDC Debezium Protocol](/ticdc/ticdc-debezium.md)
-      - [TiCDC Open Protocol](/ticdc/ticdc-open-protocol.md)
-      - [TiCDC Simple Protocol](/ticdc/ticdc-simple-protocol.md)
-    - [TiCDC Open API v2](/ticdc/ticdc-open-api-v2.md)
-    - [TiCDC Open API v1](/ticdc/ticdc-open-api.md)
-    - TiCDC Data Consumption
-      - [TiCDC Row Data Checksum Verification Based on Avro](/ticdc/ticdc-avro-checksum-verification.md)
-      - [Guide for Developing a Storage Sink Consumer](/ticdc/ticdc-storage-consumer-dev-guide.md)
-    - [TiCDC Compatibility](/ticdc/ticdc-compatibility.md)
-  - [Troubleshoot](/ticdc/troubleshoot-ticdc.md)
-  - [FAQs](/ticdc/ticdc-faq.md)
-  - [Glossary](/ticdc/ticdc-glossary.md)
 - Maintain
-  - Security
-    - [Best Practices for TiDB Security Configuration](/best-practices-for-security-configuration.md)
-    - [Enable TLS Between TiDB Clients and Servers](/enable-tls-between-clients-and-servers.md)
-    - [Enable TLS Between TiDB Components](/enable-tls-between-components.md)
-    - [Generate Self-signed Certificates](/generate-self-signed-certificates.md)
-    - [Encryption at Rest](/encryption-at-rest.md)
-    - [Enable Encryption for Disk Spill](/enable-disk-spill-encrypt.md)
-    - [Log Redaction](/log-redaction.md)
   - Upgrade
     - [Use TiUP](/upgrade-tidb-using-tiup.md)
     - [Use TiDB Operator](https://docs.pingcap.com/tidb-in-kubernetes/stable/upgrade-a-tidb-cluster)
@@ -307,6 +240,7 @@
 - Performance Tuning
   - Tuning Guide
     - [Performance Tuning Overview](/performance-tuning-overview.md)
+    - [Configure TiDB for Optimal Performance](/tidb-performance-tuning-config.md)
     - [Performance Analysis and Tuning](/performance-tuning-methods.md)
     - [Performance Tuning Practices for OLTP Scenarios](/performance-tuning-practices.md)
     - [TiFlash Performance Analysis Methods](/tiflash-performance-tuning-methods.md)
@@ -628,6 +562,48 @@
       - [FAQ](/tidb-lightning/tidb-lightning-faq.md)
       - [Glossary](/tidb-lightning/tidb-lightning-glossary.md)
   - [Dumpling](/dumpling-overview.md)
+  - TiCDC
+    - [Overview](/ticdc/ticdc-overview.md)
+    - [Deploy and Maintain](/ticdc/deploy-ticdc.md)
+    - Changefeed
+      - [Overview](/ticdc/ticdc-changefeed-overview.md)
+      - Create Changefeeds
+        - [Replicate Data to MySQL-compatible Databases](/ticdc/ticdc-sink-to-mysql.md)
+        - [Replicate Data to Kafka](/ticdc/ticdc-sink-to-kafka.md)
+        - [Replicate Data to Pulsar](/ticdc/ticdc-sink-to-pulsar.md)
+        - [Replicate Data to Storage Services](/ticdc/ticdc-sink-to-cloud-storage.md)
+      - [Manage Changefeeds](/ticdc/ticdc-manage-changefeed.md)
+      - [TiCDC Client Authentication](/ticdc/ticdc-client-authentication.md)
+      - [Log Filter](/ticdc/ticdc-filter.md)
+      - [DDL Replication](/ticdc/ticdc-ddl.md)
+      - [Bidirectional Replication](/ticdc/ticdc-bidirectional-replication.md)
+      - [Data Integrity Validation for Single-Row Data](/ticdc/ticdc-integrity-check.md)
+      - [Data Consistency Validation for TiDB Upstream/Downstream Clusters](/ticdc/ticdc-upstream-downstream-check.md)
+      - [TiCDC Behavior in Splitting UPDATE Events](/ticdc/ticdc-split-update-behavior.md)
+    - Monitor and Alert
+      - [Monitoring Metrics Summary](/ticdc/ticdc-summary-monitor.md)
+      - [Monitoring Metrics Details](/ticdc/monitor-ticdc.md)
+      - [Alert Rules](/ticdc/ticdc-alert-rules.md)
+    - Reference
+      - [Architecture](/ticdc/ticdc-architecture.md)
+      - [TiCDC Server Configurations](/ticdc/ticdc-server-config.md)
+      - [TiCDC Changefeed Configurations](/ticdc/ticdc-changefeed-config.md)
+      - Output Protocols
+        - [TiCDC Avro Protocol](/ticdc/ticdc-avro-protocol.md)
+        - [TiCDC Canal-JSON Protocol](/ticdc/ticdc-canal-json.md)
+        - [TiCDC CSV Protocol](/ticdc/ticdc-csv.md)
+        - [TiCDC Debezium Protocol](/ticdc/ticdc-debezium.md)
+        - [TiCDC Open Protocol](/ticdc/ticdc-open-protocol.md)
+        - [TiCDC Simple Protocol](/ticdc/ticdc-simple-protocol.md)
+      - [TiCDC Open API v2](/ticdc/ticdc-open-api-v2.md)
+      - [TiCDC Open API v1](/ticdc/ticdc-open-api.md)
+      - TiCDC Data Consumption
+        - [TiCDC Row Data Checksum Verification Based on Avro](/ticdc/ticdc-avro-checksum-verification.md)
+        - [Guide for Developing a Storage Sink Consumer](/ticdc/ticdc-storage-consumer-dev-guide.md)
+      - [Compatibility](/ticdc/ticdc-compatibility.md)
+    - [Troubleshoot](/ticdc/troubleshoot-ticdc.md)
+    - [FAQs](/ticdc/ticdc-faq.md)
+    - [Glossary](/ticdc/ticdc-glossary.md)
   - PingCAP Clinic Diagnostic Service
     - [Overview](/clinic/clinic-introduction.md)
     - [Quick Start](/clinic/quick-start-with-clinic.md)
@@ -643,7 +619,6 @@
   - TiProxy
     - [Overview](/tiproxy/tiproxy-overview.md)
     - [Load Balancing Policies](/tiproxy/tiproxy-load-balance.md)
-    - [Traffic Replay](/tiproxy/tiproxy-traffic-replay.md)
     - [Configuration](/tiproxy/tiproxy-configuration.md)
     - [Command Line Parameters](/tiproxy/tiproxy-command-line-flags.md)
     - [Monitoring Metrics](/tiproxy/tiproxy-grafana.md)
@@ -676,7 +651,6 @@
     - [TiFlash Late Materialization](/tiflash/tiflash-late-materialization.md)
     - [Spill to Disk](/tiflash/tiflash-spill-disk.md)
     - [Data Validation](/tiflash/tiflash-data-validation.md)
-    - [MinTSO Scheduler](/tiflash/tiflash-mintso-scheduler.md)
     - [Compatibility](/tiflash/tiflash-compatibility.md)
     - [Pipeline Execution Model](/tiflash/tiflash-pipeline-model.md)
   - TiDB Distributed eXecution Framework (DXF)
@@ -708,6 +682,13 @@
     - [TiFlash](/tiflash/monitor-tiflash.md)
     - [TiCDC](/ticdc/monitor-ticdc.md)
     - [Resource Control](/grafana-resource-control-dashboard.md)
+  - Security
+    - [Enable TLS Between TiDB Clients and Servers](/enable-tls-between-clients-and-servers.md)
+    - [Enable TLS Between TiDB Components](/enable-tls-between-components.md)
+    - [Generate Self-signed Certificates](/generate-self-signed-certificates.md)
+    - [Encryption at Rest](/encryption-at-rest.md)
+    - [Enable Encryption for Disk Spill](/enable-disk-spill-encrypt.md)
+    - [Log Redaction](/log-redaction.md)
   - Privileges
     - [Security Compatibility with MySQL](/security-compatibility-with-mysql.md)
     - [Privilege Management](/privilege-management.md)
@@ -739,6 +720,7 @@
       - [`ADMIN RESUME DDL`](/sql-statements/sql-statement-admin-resume-ddl.md)
       - [`ADMIN [SET|SHOW|UNSET] BDR ROLE`](/sql-statements/sql-statement-admin-bdr-role.md)
       - [`ADMIN SHOW DDL [JOBS|JOB QUERIES]`](/sql-statements/sql-statement-admin-show-ddl.md)
+      - [`ADMIN SHOW TELEMETRY`](/sql-statements/sql-statement-admin-show-telemetry.md)
       - [`ALTER DATABASE`](/sql-statements/sql-statement-alter-database.md)
       - [`ALTER INSTANCE`](/sql-statements/sql-statement-alter-instance.md)
       - [`ALTER PLACEMENT POLICY`](/sql-statements/sql-statement-alter-placement-policy.md)
@@ -888,7 +870,6 @@
       - [Date and Time Types](/data-type-date-and-time.md)
       - [String Types](/data-type-string.md)
       - [JSON Type](/data-type-json.md)
-      - [Vector Types](/vector-search-data-types.md)
     - Functions and Operators
       - [Overview](/functions-and-operators/functions-and-operators-overview.md)
       - [Type Conversion in Expression Evaluation](/functions-and-operators/type-conversion-in-expression-evaluation.md)
@@ -902,7 +883,6 @@
       - [Encryption and Compression Functions](/functions-and-operators/encryption-and-compression-functions.md)
       - [Locking Functions](/functions-and-operators/locking-functions.md)
       - [Information Functions](/functions-and-operators/information-functions.md)
-      - [Vector Functions and Operators](/vector-search-functions-and-operators.md)
       - JSON Functions
         - [Overview](/functions-and-operators/json-functions.md)
         - [Functions That Create JSON](/functions-and-operators/json-functions/json-functions-create.md)
@@ -923,7 +903,6 @@
       - [TiDB Specific Functions](/functions-and-operators/tidb-functions.md)
       - [Comparisons between Functions and Syntax of Oracle and TiDB](/oracle-functions-to-tidb.md)
     - [Clustered Indexes](/clustered-indexes.md)
-    - [Vector Index](/vector-search-index.md)
     - [Constraints](/constraints.md)
     - [Generated Columns](/generated-columns.md)
     - [SQL Mode](/sql-mode.md)
@@ -1017,7 +996,6 @@
         - [`schema_unused_indexes`](/sys-schema/sys-schema-unused-indexes.md)
     - [Metadata Lock](/metadata-lock.md)
     - [TiDB Accelerated Table Creation](/accelerated-table-creation.md)
-    - [Schema Cache](/schema-cache.md)
   - UI
     - TiDB Dashboard
       - [Overview](/dashboard/dashboard-intro.md)
@@ -1072,8 +1050,6 @@
   - [Release Timeline](/releases/release-timeline.md)
   - [TiDB Versioning](/releases/versioning.md)
   - [TiDB Installation Packages](/binary-package.md)
-  - v8.4
-    - [8.4.0-DMR](/releases/release-8.4.0.md)
   - v8.3
     - [8.3.0-DMR](/releases/release-8.3.0.md)
   - v8.2
@@ -1086,7 +1062,6 @@
   - v7.6
     - [7.6.0-DMR](/releases/release-7.6.0.md)
   - v7.5
-    - [7.5.4](/releases/release-7.5.4.md)
     - [7.5.3](/releases/release-7.5.3.md)
     - [7.5.2](/releases/release-7.5.2.md)
     - [7.5.1](/releases/release-7.5.1.md)
@@ -1098,7 +1073,6 @@
   - v7.2
     - [7.2.0-DMR](/releases/release-7.2.0.md)
   - v7.1
-    - [7.1.6](/releases/release-7.1.6.md)
     - [7.1.5](/releases/release-7.1.5.md)
     - [7.1.4](/releases/release-7.1.4.md)
     - [7.1.3](/releases/release-7.1.3.md)
diff --git a/markdown-pages/en/tidb/master/media/key-settings/instance-plan-cache.png b/markdown-pages/en/tidb/master/media/key-settings/instance-plan-cache.png
new file mode 100644
index 0000000..5ebfa15
Binary files /dev/null and b/markdown-pages/en/tidb/master/media/key-settings/instance-plan-cache.png differ
diff --git a/markdown-pages/en/tidb/master/media/key-settings/titan-rocksdb-compactions.png b/markdown-pages/en/tidb/master/media/key-settings/titan-rocksdb-compactions.png
new file mode 100644
index 0000000..1d57fc2
Binary files /dev/null and b/markdown-pages/en/tidb/master/media/key-settings/titan-rocksdb-compactions.png differ
diff --git a/markdown-pages/en/tidb/master/tidb-performance-tuning-config.md b/markdown-pages/en/tidb/master/tidb-performance-tuning-config.md
new file mode 100644
index 0000000..8492137
--- /dev/null
+++ b/markdown-pages/en/tidb/master/tidb-performance-tuning-config.md
@@ -0,0 +1,533 @@
+---
+title: Configure TiDB for Optimal Performance
+summary: Learn how to optimize TiDB performance by configuring key settings and addressing edge cases.
+---
+
+## Configure TiDB for Optimal Performance
+
+This guide describes how to optimize the performance of TiDB, including:
+
+- Best practices for common workloads.
+- Strategies for handling challenging performance scenarios.
+
+> **Note:**
+>
+> The optimization techniques in this guide can help achieve optimal performance in TiDB. However, performance tuning often involves balancing multiple factors, and no single solution addresses all performance needs. Some techniques in this guide use experimental features, which are marked accordingly. Although these optimizations can significantly improve performance, they might not be suitable for production environments and require careful evaluation before implementation.
+
+## Overview
+
+Optimizing TiDB for peak performance requires careful tuning of various settings. In many cases, achieving optimal performance involves adjusting configurations beyond their default values.
+
+The default settings prioritize stability over performance. To maximize performance, you might need to use more aggressive configurations and, in some cases, experimental features. These recommendations are based on production deployment experience and performance optimization research.
+
+This guide describes the non-default settings, including their benefits and potential trade-offs. Use this information to optimize TiDB settings for your workload requirements.
+
+## Key settings for common workloads
+
+The following settings are commonly used to optimize TiDB performance:
+
+- Enhance execution plan cache, such as [Instance-level execution plan cache](/sql-prepared-plan-cache.md), [Non-prepared plan cache](/sql-non-prepared-plan-cache.md), and [Instance-level execution plan cache](/system-variables.md#tidb_enable_instance_plan_cache-new-in-v840).
+- Optimize the behavior of the TiDB optimizer by using [Optimizer Fix Controls](/optimizer-fix-controls.md).
+- Use the [Titan](/storage-engine/titan-overview.md) storage engine more aggressively.
+
+These settings can significantly improve performance for many workloads. However, as with any optimization, thoroughly test them in your environment before deploying to production.
+
+### System variables
+
+Execute the following SQL commands to apply the recommended settings:
+
+```sql
+SET GLOBAL tidb_enable_instance_plan_cache=on;
+SET GLOBAL tidb_instance_plan_cache_max_size=2GiB;
+SET GLOBAL tidb_enable_non_prepared_plan_cache=on;
+SET GLOBAL tidb_ignore_prepared_cache_close_stmt=on;
+SET GLOBAL tidb_enable_inl_join_inner_multi_pattern=on;
+SET GLOBAL tidb_opt_derive_topn=on;
+SET GLOBAL tidb_runtime_filter_mode=LOCAL;
+SET GLOBAL tidb_opt_enable_mpp_shared_cte_execution=on;
+SET GLOBAL tidb_rc_read_check_ts=on;
+SET GLOBAL tidb_guarantee_linearizability=off;
+SET GLOBAL pd_enable_follower_handle_region=on;
+SET GLOBAL tidb_opt_fix_control = '44262:ON,44389:ON,44823:10000,44830:ON,44855:ON,52869:ON';
+```
+
+The following table outlines the impact of specific system variable configurations:
+
+| System variable | Description | Note |
+| ---------| ---- | ----|
+| [`tidb_enable_instance_plan_cache`](/system-variables.md#tidb_enable_instance_plan_cache-new-in-v840) and [`tidb_instance_plan_cache_max_size`](/system-variables.md#tidb_instance_plan_cache_max_size-new-in-v840)| Use instance-level plan cache instead of session-level caching. This significantly improves performance for workloads with high connection counts or frequent prepared statement usage. | This is an experimental feature. Test in non-production environments first and monitor memory usage as the plan cache size increases. |
+| [`tidb_enable_non_prepared_plan_cache`](/system-variables.md#tidb_enable_non_prepared_plan_cache)| Enable the [Non-prepared plan cache](/sql-non-prepared-plan-cache.md) feature to reduce compile costs for applications that do not use prepared statements. | N/A |
+| [`tidb_ignore_prepared_cache_close_stmt`](/system-variables.md#tidb_ignore_prepared_cache_close_stmt-new-in-v600)| Cache plans for applications that use prepared statements but close the plan after each execution. | N/A |
+| [`tidb_enable_inl_join_inner_multi_pattern`](/system-variables.md#tidb_enable_inl_join_inner_multi_pattern-new-in-v700)| Enable Index Join support when the inner table has `Selection` or `Projection` operators on it. | N/A | 
+| [`tidb_opt_derive_topn`](/system-variables.md#tidb_opt_derive_topn-new-in-v700)| Enable the optimization rule of [Deriving TopN or Limit from window functions](/derive-topn-from-window.md). | This is limited to the `ROW_NUMBER()` window function. | 
+| [`tidb_runtime_filter_mode`](/system-variables.md#tidb_runtime_filter_mode-new-in-v720)| Enable [Runtime Filter](/runtime-filter.md#runtime-filter-mode) in the local mode to improve hash join efficiency. | The variable is introduced in v7.2.0 and is disabled by default for safety. | 
+| [`tidb_opt_enable_mpp_shared_cte_execution`](/system-variables.md#tidb_opt_enable_mpp_shared_cte_execution-new-in-v720)| Enable non-recursive [Common Table Expressions (CTE)](/sql-statements/sql-statement-with.md) pushdown to TiFlash. | This is an experimental feature. | 
+| [`tidb_rc_read_check_ts`](/system-variables.md#tidb_rc_read_check_ts-new-in-v600)| For the read-committed isolation level, enabling this variable avoids the latency and cost of getting the global timestamp and optimizes transaction-level read latency. | This feature is incompatible with the Repeatable Read isolation level. | 
+| [`tidb_guarantee_linearizability`](/system-variables.md#tidb_guarantee_linearizability-new-in-v50)| Improve performance by skipping the commit timestamp fetch from the PD server. | This sacrifices linearizability in favor of performance. Only causal consistency is guaranteed. It is not suitable for scenarios requiring strict linearizability. |
+| [`pd_enable_follower_handle_region`](/system-variables.md#pd_enable_follower_handle_region-new-in-v760)| Activate the PD Follower feature, allowing PD followers to process Region requests. This helps distribute load evenly across all PD servers and reduces CPU pressure on the PD leader. | This is an experimental feature. Test in non-production environments. |
+| [`tidb_opt_fix_control`](/optimizer-fix-controls.md#tidb_opt_fix_control) | Enable advanced query optimization strategies to improve performance through additional optimization rules and heuristics. | Test thoroughly in your environment, as performance improvements vary by workload. |
+
+The following describes the optimizer control configurations that enable additional optimizations:
+
+- [`44262:ON`](/optimizer-fix-controls.md#44262-new-in-v653-and-v720): Use [Dynamic pruning mode](/partitioned-table.md#dynamic-pruning-mode) to access the partitioned table when the [GlobalStats](/statistics.md#collect-statistics-of-partitioned-tables-in-dynamic-pruning-mode) are missing.
+- [`44389:ON`](/optimizer-fix-controls.md#44389-new-in-v653-and-v720): For filters such as `c = 10 and (a = 'xx' or (a = 'kk' and b = 1))`, build more comprehensive scan ranges for `IndexRangeScan`.
+- [`44823:10000`](/optimizer-fix-controls.md#44823-new-in-v730): To save memory, plan cache does not cache queries with parameters exceeding the specified number of this variable. Increase plan cache parameter limit from `200` to `10000` to make plan cache available for query with long in-lists.
+- [`44830:ON`](/optimizer-fix-controls.md#44830-new-in-v730): Plan cache is allowed to cache execution plans with the `PointGet` operator generated during physical optimization.
+- [`44855:ON`](/optimizer-fix-controls.md#44855-new-in-v730): The optimizer selects `IndexJoin` when the `Probe` side of an `IndexJoin` operator contains a `Selection` operator.
+- [`52869:ON`](/optimizer-fix-controls.md#52869-new-in-v810): The optimizer chooses index merge automatically if the optimizer can choose the single index scan method (other than full table scan) for a query plan.
+
+### TiDB configurations
+
+Add the following configuration items to the TiDB configuration file:
+
+```toml
+[performance]
+concurrently-init-stats = true
+force-init-stats = true
+lite-init-stats = false
+```
+
+| Configuration item | Description | Note | 
+| ---------| ---- | ----|
+| [`concurrently-init-stats`](/tidb-configuration-file.md#concurrently-init-stats-new-in-v810-and-v752), [`force-init-stats`](/tidb-configuration-file.md#force-init-stats-new-in-v657-and-v710), and [`lite-init-stats`](/tidb-configuration-file.md#lite-init-stats-new-in-v710) | Ensure the concurrent and comprehensive loading of table statistics during TiDB startup, which improves initial query optimization performance. | Might increase startup duration and memory usage. |
+
+### TiKV configurations
+
+Add the following configuration items to the TiKV configuration file:
+
+```toml
+[server]
+concurrent-send-snap-limit = 64
+concurrent-recv-snap-limit = 64
+snap-io-max-bytes-per-sec = "400MiB"
+
+[pessimistic-txn]
+in-memory-peer-size-limit = "32MiB"
+in-memory-instance-size-limit = "512MiB"
+
+[rocksdb.titan]
+enabled = true
+[rocksdb.defaultcf.titan]
+min-blob-size = "1KB"
+blob-file-compression = "zstd"
+
+[storage.flow-control]
+l0-files-threshold = 60
+```
+
+| Configuration item | Description | Note |
+| ---------| ---- | ----|
+| [`concurrent-send-snap-limit`](/tikv-configuration-file.md#concurrent-send-snap-limit), [`concurrent-recv-snap-limit`](/tikv-configuration-file.md#concurrent-recv-snap-limit), and [`snap-io-max-bytes-per-sec`](/tikv-configuration-file.md#snap-io-max-bytes-per-sec) | Set limits for concurrent snapshot transfer and I/O bandwidth during TiKV scaling operations. Higher limits reduce scaling time by allowing faster data migration. | Adjusting these limits affects the trade-off between scaling speed and online transaction performance. |
+| [`in-memory-peer-size-limit`](/tikv-configuration-file.md#in-memory-peer-size-limit-new-in-v840) and [`in-memory-instance-size-limit`](/tikv-configuration-file.md#in-memory-instance-size-limit-new-in-v840) | Control the memory allocation for pessimistic lock caching at the Region and TiKV instance levels. Storing locks in memory reduces disk I/O and improves transaction performance. | Monitor memory usage carefully. Higher limits improve performance but increase memory consumption. |
+| [`rocksdb.titan`](/tikv-configuration-file.md#rocksdbtitan), [`rocksdb.defaultcf.titan`](/tikv-configuration-file.md#rocksdbdefaultcftitan), [`min-blob-size`](/tikv-configuration-file.md#min-blob-size), and [`blob-file-compression`](/tikv-configuration-file.md#blob-file-compression) | Enable the Titan storage engine to reduce write amplification and alleviate disk I/O bottlenecks. Particularly useful when RocksDB compaction cannot keep up with write workloads, resulting in accumulated pending compaction bytes. | Enable it when write amplification is the primary bottleneck. Trade-offs include: 1. Potential performance impact on primary key range scans. 2. Increased space amplification (up to 2x in the worst case). 3. Additional memory usage for blob cache. |
+| [`storage.flow-control.l0-files-threshold`](/tikv-configuration-file.md#l0-files-threshold) | Control when write flow control is triggered based on the number of kvDB L0 files. Increasing the threshold reduces write stalls during high write workloads. | Higher thresholds might lead to more aggressive compactions when many L0 files exist. |
+
+### TiFlash configurations
+
+Add the following configuration items to the TiFlash configuration file:
+
+```toml
+[raftstore-proxy.server]
+snap-io-max-bytes-per-sec = "300MiB"
+```
+
+| Configuration item | Description | Note |
+| ---------| ---- | ----|
+| [`snap-io-max-bytes-per-sec`](/tikv-configuration-file.md#snap-io-max-bytes-per-sec) | Control the maximum allowable disk bandwidth for data replication from TiKV to TiFlash. Higher limits accelerate initial data loading and catch-up replication. | Higher bandwidth consumption might impact online transaction performance. Balance between replication speed and system stability. |
+
+## Benchmark 
+
+This section compares performance between default settings (baseline) and optimized settings based on the preceding [key settings for common loads](#key-settings-for-common-workloads).
+
+### Sysbench workloads on 1000 tables
+
+#### Test environment
+
+The test environment is as follows:
+
+- 3 TiDB servers (16 cores, 64 GiB)
+- 3 TiKV servers (16 cores, 64 GiB)
+- TiDB version: v8.4.0
+- Workload: [sysbench oltp_read_only](https://github.com/akopytov/sysbench/blob/master/src/lua/oltp_read_only.lua)
+
+#### Performance comparison
+
+The following table compares throughput, latency, and plan cache hit ratio between baseline and optimized settings.
+
+| Metric | Baseline | Optimized | Improvement |
+| ---------| ---- | ----| ----|
+| QPS | 89,100 | 100,128 | +12.38% |
+| Average latency (ms)|35.87 | 31.92 | -11.01% |
+| P95 latency (ms)| 58.92 | 51.02 | -13.41% |
+| Plan cache hit ratio (%) | 56.89% | 87.51% | +53.82% |
+| Plan cache memory usage (MiB) | 95.3 | 70.2 | -26.34% |
+
+#### Key Benefits
+
+The instance plan cache demonstrates significant performance improvements over the baseline configuration:
+
+- Higher hit ratio: increases by 53.82% (from 56.89% to 87.51%).
+- Lower memory usage: decreases by 26.34% (from 95.3 MiB to 70.2 MiB).
+- Better performance:
+
+    - QPS increases by 12.38%.
+    - Average latency decreases by 11.01%.
+    - P95 latency decreases by 13.41%.
+
+#### How it works
+
+Instance plan cache improves performance through these mechanisms:
+
+- Cache execution plans for `SELECT` statements in memory.
+- Share cached plans across all connections (up to 200) on the same TiDB instance.
+- Can effectively store plans for up to 5,000 `SELECT` statements across 1,000 tables.
+- Cache misses primarily occur only for `BEGIN` and `COMMIT` statements.
+
+#### Real-world benefits
+
+Although the benchmark using simple sysbench `oltp_read_only` queries (14 KB per plan) shows modest improvements, you can expect greater benefits in real-word applications:
+
+- Complex queries can run up to 20 times faster.
+- Memory usage is more efficient compared to session-level plan cache.
+
+Instance plan cache is particularly effective for systems with:
+
+- Large tables with many columns.
+- Complex SQL queries.
+- High concurrent connections.
+- Diverse query patterns.
+
+#### Memory efficiency
+
+Instance plan cache provides better memory efficiency than session-level plan cache because:
+
+- Plans are shared across all connections
+- No need to duplicate plans for each session
+- More efficient memory utilization while maintaining higher hit ratios
+
+In scenarios with multiple connections and complex queries, session-level plan cache would require significantly more memory to achieve similar hit ratios, making instance plan cache the more efficient choice.
+
+![instance-plan-cache](/media/key-settings/instance-plan-cache.png)
+
+#### Test workload
+
+The following `sysbench oltp_read_only prepare` command loads data:
+
+```bash
+sysbench oltp_read_only prepare --mysql-host={host} --mysql-port={port} --mysql-user=root --db-driver=mysql --mysql-db=test --threads=100 --time=900 --report-interval=10 --tables=1000 --table-size=10000
+```
+
+The following `sysbench oltp_read_only run` command runs workload:
+
+```bash
+sysbench oltp_read_only run --mysql-host={host} --mysql-port={port} --mysql-user=root --db-driver=mysql --mysql-db=test --threads=200 --time=900 --report-interval=10 --tables=1000 --table-size=10000
+```
+
+For more information, see [How to Test TiDB Using Sysbench](/benchmark/benchmark-tidb-using-sysbench.md).
+
+### YCSB workloads on large record value
+
+#### Test environment
+
+The test environment is as follows:
+
+- 3 TiDB servers (16 cores, 64 GiB)
+- 3 TiKV servers (16 cores, 64 GiB)
+- TiDB version: v8.4.0
+- Workload: [go-ycsb workloada](https://github.com/pingcap/go-ycsb/blob/master/workloads/workloada)
+
+#### Performance comparison
+
+The following table compares throughput (operations per second) between the baseline and optimized settings.
+
+| Item | Baseline (OPS) | Optimized (OPS) | Improvement |
+| ---------| ---- | ----| ----|
+| load data | 2858.5 | 5074.3 | +77.59% |
+| workloada | 2243.0 | 12804.3 | +470.86% |
+
+#### Performance analysis
+
+Titan is enabled by default starting from v7.6.0 and the default `min-blob-size` of Titan in TiDB v8.4.0 is `32KiB`. The baseline configuration uses a record size of `31KiB` to ensure data is stored in RocksDB. In contrast, for the key settings configuration, set `min-blob-size` to `1KiB`, causing data to be stored in Titan.
+
+The performance improvement observed in the Key Settings is primarily attributed to Titan's ability to reduce RocksDB compactions. As shown in the following figures:
+
+- Baseline: The total throughput of RocksDB compaction exceeds 1 GiB/s, with peaks over 3 GiB/s.
+- Key Settings: The peak throughput of RocksDB compaction remains below 100 MiB/s.
+
+This significant reduction in compaction overhead contributes to the overall throughput improvement seen in the Key Settings configuration.
+
+![titan-rocksdb-compactions](/media/key-settings/titan-rocksdb-compactions.png)
+
+#### Test workload
+
+The following `go-ycsb load` command loads data:
+
+```bash
+go-ycsb load mysql -P /ycsb/workloads/workloada -p {host} -p mysql.port={port} -p threadcount=100 -p recordcount=5000000 -p operationcount=5000000 -p workload=core -p requestdistribution=uniform -pfieldcount=31 -p fieldlength=1024
+```
+
+The following `go-ycsb run` command runs workload:
+
+```bash
+go-ycsb run mysql -P /ycsb/workloads/workloada -p {host} -p mysql.port={port} -p mysql.db=test -p threadcount=100 -p recordcount=5000000 -p operationcount=5000000 -p workload=core -prequestdistribution=uniform -p fieldcount=31 -p fieldlength=1024
+```
+
+## Edge cases and optimizations
+
+This section shows you how to optimize TiDB for specific scenarios that need targeted adjustments beyond basic optimizations. You will learn how to tune TiDB for your particular use cases.
+
+### Identify edge cases
+
+To identify edge cases, perform the following steps:
+
+1. Analyze query patterns and workload characteristics.
+2. Monitor system metrics to identify performance bottlenecks.
+3. Gather feedback from application teams about specific issues.
+
+### Common edge cases
+
+The following lists some common edge cases:
+
+- High TSO wait for high-frequency small queries
+- Choose the proper max chunk size for different workloads
+- Tune coprocessor cache for read-heavy workloads
+- Optimize chunk size for workload characteristics
+- Optimize transaction mode and DML type for different workloads
+- Optimize `GROUP BY` and `DISTINCT` operations with TiKV pushdown
+- Mitigate MVCC version accumulation using in-memory engine
+- Optimize statistics collection during batch operations
+- Optimize thread pool settings for different instance types
+
+The following sections explain how to handle each of these cases. You need to adjust different parameters or use specific TiDB features for each scenario.
+
+> **Note:**
+>
+> Apply these optimizations carefully and test thoroughly, as their effectiveness might vary based on your use case and data patterns.
+
+### High TSO wait for high-frequency small queries
+
+#### Troubleshooting
+
+If your workload involves frequent small transactions or queries that frequently request timestamps, [TSO (Timestamp Oracle)](/glossary.md#tso) can become a performance bottleneck. To check if TSO wait time is impacting your system, check the [**Performance Overview > SQL Execute Time Overview**](/grafana-performance-overview-dashboard.md#sql-execute-time-overview) panel. If TSO wait time constitutes a large portion of your SQL execution time, consider the following optimizations:
+
+- Use low-precision TSO (enable [`tidb_low_resolution_tso`](/system-variables.md#tidb_low_resolution_tso)) for read operations that do not need strict consistency. For more information, see [Solution 1: use low-precision TSO](#solution-1-low-precision-tso).
+- Enable [`tidb_enable_batch_dml`](/system-variables.md#tidb_enable_batch_dml) to reduce TSO requests for batch operations
+- Combine small transactions into larger ones where possible. For more information, see [Solution 2: parallel mode for TSO requests](#solution-2-parallel-mode-for-tso-requests).
+
+#### Solution 1: low-precision TSO
+
+You can reduce TSO wait time by enabling the low-precision TSO feature ([`tidb_low_resolution_tso`](/system-variables.md#tidb_low_resolution_tso)). After this feature is enabled, TiDB uses the cached timestamp to read data, reducing TSO wait time at the expense of potentially stale reads.
+
+This optimization is particularly effective in the following scenarios:
+
+- Read-heavy workloads where slight staleness is acceptable.
+- Scenarios where reducing query latency is more important than absolute consistency.
+- Applications that can tolerate reads that are a few seconds behind the latest committed state.
+
+Benefits and trade-offs:
+
+- Reduce query latency by enabling stale reads with a cached TSO, eliminating the need to request new timestamps.
+- Balance performance against data consistency: this feature is only suitable for scenarios where stale reads are acceptable. It is not recommended to use it when strict data consistency is required.
+
+To enable this optimization:
+
+```sql
+SET GLOBAL tidb_low_resolution_tso=ON;
+```
+
+#### Solution 2: parallel mode for TSO requests
+
+The [`tidb_tso_client_rpc_mode`](/system-variables.md#tidb_tso_client_rpc_mode-new-in-v840) system variable switches the mode in which TiDB sends TSO RPC requests to PD. The default value is `DEFAULT`. When the following conditions are met, you can consider switching this variable to `PARALLEL` or `PARALLEL-FAST` for potential performance improvements:
+
+- TSO waiting time constitutes a significant portion of the total execution time of SQL queries.
+- The TSO allocation in PD has not reached its bottleneck.
+- PD and TiDB nodes have sufficient CPU resources.
+- The network latency between TiDB and PD is significantly higher than the time PD takes to allocate TSO (that is, network latency accounts for the majority of TSO RPC duration).
+    - To get the duration of TSO RPC requests, check the **PD TSO RPC Duration** panel in the PD Client section of the Grafana TiDB dashboard.
+    - To get the duration of PD TSO allocation, check the **PD server TSO handle duration** panel in the TiDB section of the Grafana PD dashboard.
+- The additional network traffic resulting from more TSO RPC requests between TiDB and PD (twice for `PARALLEL` or four times for `PARALLEL-FAST`) is acceptable.
+
+To switch the parallel mode, execute the following command:
+
+```sql
+-- Use the PARALLEL mode
+SET GLOBAL tidb_tso_client_rpc_mode=PARALLEL;
+
+-- Use the PARALLEL-FAST mode
+SET GLOBAL tidb_tso_client_rpc_mode=PARALLEL-FAST;
+```
+
+### Tune coprocessor cache for read-heavy workloads
+
+You can improve query performance for read-heavy workloads by optimizing the [coprocessor cache](/coprocessor-cache.md). This cache stores the results of coprocessor requests, reducing repeated computations of frequently accessed data. To optimize cache performance, perform the following steps:
+
+1. Monitor the cache hit ratio using the metrics described in [Coprocessor Cache](/coprocessor-cache.md#view-the-grafana-monitoring-panel).
+2. Increase the cache size to improve hit rates for larger working sets.
+3. Adjust the admission threshold based on query patterns.
+
+The following lists some recommended settings for a read-heavy workload:
+
+```toml
+[tikv-client.copr-cache]
+capacity-mb = 4096
+admission-max-ranges = 5000
+admission-max-result-mb = 10
+admission-min-process-ms = 0
+```
+
+### Optimize chunk size for workload characteristics
+
+The [`tidb_max_chunk_size`](system-variables.md#tidb_max_chunk_size) system variable sets the maximum number of rows in a chunk during the execution process. Adjusting this value based on your workload can improve performance.
+
+- For OLTP workloads with large concurrency and small transactions:
+
+    - Set the value between `128` and `256` rows (the default value is `1024`).
+    - This reduces memory usage and makes limit queries faster.
+    - Use case: point queries, small range scans.
+
+    ```sql
+    SET GLOBAL tidb_max_chunk_size = 128;
+    ```
+
+- For OLAP or analytical workloads with complex queries and large result sets:
+
+    - Set the value between `1024` and `4096` rows.
+    - This increases throughput when scanning large amounts of data.
+    - Use case: aggregations, large table scans.
+
+    ```sql
+    SET GLOBAL tidb_max_chunk_size = 4096;
+    ```
+
+### Optimize transaction mode and DML type for different workloads
+
+TiDB provides different transaction modes and DML execution types to optimize performance for various workload patterns.
+
+#### Transaction modes
+
+You can set the transaction mode using the [`tidb_txn_mode`](/system-variables.md#tidb_txn_mode) system variable.
+
+- [Pessimistic transaction mode](/pessimistic-transaction.md) (default):
+
+    - Suitable for general workloads with potential write conflicts.
+    - Provides stronger consistency guarantees.
+
+    ```sql
+    SET SESSION tidb_txn_mode = "pessimistic";
+    ```
+
+- [Optimistic transaction mode](/optimistic-transaction.md):
+
+    - Suitable for workloads with minimal write conflicts.
+    - Better performance for multi-statement transactions.
+    - Example: `BEGIN; INSERT...; INSERT...; COMMIT;`.
+
+    ```sql
+    SET SESSION tidb_txn_mode = "optimistic";
+    ```
+
+#### DML types
+
+You can control the execution mode of DML statements using the [`tidb_dml_type`](/system-variables.md#tidb_dml_type-new-in-v800) system variable, which is introduced in v8.0.0.
+
+To use the bulk DML execution mode, set `tidb_dml_type` to `"bulk"`. This mode optimizes bulk data loading without conflicts and reduces memory usage during large write operations. Before using this mode, ensure that:
+
+- Auto-commit is enabled.
+- The [`pessimistic-auto-commit`](/tidb-configuration-file.md#pessimistic-auto-commit-new-in-v600) configuration item is set to `false`.
+
+```sql
+SET SESSION tidb_dml_type = "bulk";
+```
+
+### Optimize `GROUP BY` and `DISTINCT` operations with TiKV pushdown
+
+TiDB pushes down aggregation operations to TiKV to reduce data transfer and processing overhead. The performance improvement varies based on your data characteristics.
+
+#### Usage scenarios
+
+- **Ideal scenarios** (high performance gain):
+    - Columns containing few distinct values (low NDV).
+    - Data containing frequent duplicate values.
+    - Example: status columns, category codes, date parts.
+
+- **Non-ideal scenarios** (potential performance loss):
+    - Columns containing mostly unique values (high NDV).
+    - Unique identifiers or timestamps.
+    - Example: User IDs, transaction IDs.
+
+#### Configuration
+
+Enable pushdown optimizations at the session or global level:
+
+```sql
+-- Enable regular aggregation pushdown
+SET GLOBAL tidb_opt_agg_push_down = ON;
+
+-- Enable distinct aggregation pushdown
+SET GLOBAL tidb_opt_distinct_agg_push_down = ON;
+```
+
+### Mitigate MVCC version accumulation using in-memory engine
+
+Excessive MVCC versions can cause performance bottlenecks, particularly in high read/write areas or due to issues with garbage collection and compaction. You can use the [in-memory engine](/tikv-in-memory-engine.md) introduced in v8.5.0 to mitigate this issue. To enable it, add the following configuration to your TiKV configuration file.
+
+> **Note:**
+>
+> The in-memory engine helps reduce the impact of excessive MVCC versions but might increase memory usage. Monitor your system after enabling this feature.
+
+```toml
+[in-memory-engine]
+enable = true
+```
+
+### Optimize statistics collection during batch operations
+
+You can optimize performance during batch operations while maintaining query optimization by managing statistics collection. This section describes how to manage this process effectively.
+
+#### When to disable auto analyze
+
+You can disable auto analyze by setting the [`tidb_enable_auto_analyze`](/system-variables.md#tidb_enable_auto_analyze-new-in-v610) system variable to `OFF` in the following scenarios:
+
+- During large data imports.
+- During bulk update operations.
+- For time-sensitive batch processing.
+- When you need full control over the timing of statistics collection.
+
+#### Best practices
+
+- Before the batch operation:
+
+   ```sql
+   -- Disable auto analyze
+   SET GLOBAL tidb_enable_auto_analyze = OFF;
+   ```
+
+- After the batch operation:
+
+   ```sql
+   -- Manually collect statistics
+   ANALYZE TABLE your_table;
+   
+   -- Re-enable auto analyze
+   SET GLOBAL tidb_enable_auto_analyze = ON;
+   ```
+
+### Optimize thread pool settings for different instance types
+
+To improve TiKV performance, configure the thread pools based on your instance's CPU resources. The following guidelines help you optimize these settings:
+
+- For instances with 8 to 16 cores, the default settings are typically sufficient.
+
+- For instances with 32 or more cores, increase the pool sizes for better resource utilization. Adjust the settings as follows:
+
+    ```toml
+    [server]
+    # Increase gRPC thread pool 
+    grpc-concurrency = 10
+    
+    [raftstore]
+    # Optimize for write-intensive workloads
+    apply-pool-size = 4
+    store-pool-size = 4
+    store-io-pool-size = 2
+    ```
\ No newline at end of file