fix bug in performance tuning practices (#18615) (#18628)

pingcap · Aug 20, 2024 · e01f092 · e01f092
1 parent ea511d7
commit e01f092
Showing 1 changed file with 1 addition and 1 deletion.
diff --git 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.