From f7dbd001c6760ba68a9ed97fad793f75b427d6f1 Mon Sep 17 00:00:00 2001 From: Ti Chi Robot Date: Tue, 20 Aug 2024 16:01:42 +0800 Subject: [PATCH] fix bug in performance tuning practices (#18615) (#18634) --- performance-tuning-practices.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/performance-tuning-practices.md b/performance-tuning-practices.md index 13a52c0db9730..4e6e77272d755 100644 --- a/performance-tuning-practices.md +++ b/performance-tuning-practices.md @@ -427,7 +427,7 @@ By comparing the performance of each scenario, we can draw the following conclus - TiDB is compatible with different commands of the MySQL protocol. When using the Prepared Statement interface and setting the following JDBC connection parameters, the application can achieve its best performance: ``` - useServerPrepStmts=true&cachePrepStmts=true&prepStmtCacheSize=1000&prepStmtCacheSqlLimit=20480&useConfigs= maxPerformance + useServerPrepStmts=true&cachePrepStmts=true&prepStmtCacheSize=1000&prepStmtCacheSqlLimit=20480&useConfigs=maxPerformance ``` - It is recommended that you use TiDB Dashboard (for example, the Top SQL feature and Continuous Profiling feature) and Performance Overview dashboard for performance analysis and tuning.