Tune TiKV: change the default value of grpc-concurrency (#6531)

pingcap · Sep 26, 2021 · 3c2e0ff · 3c2e0ff
1 parent b3bd7db
commit 3c2e0ff
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/tune-tikv-thread-performance.md b/tune-tikv-thread-performance.md
@@ -37,7 +37,7 @@ Starting from TiKV v5.0, all read requests use the unified thread pool for queri
 
 * The gRPC thread pool.
 
- The default size (configured by `server.grpc-concurrency`) of the gRPC thread pool is `4`. This thread pool has almost no computing overhead and is mainly responsible for network I/O and deserialization requests, so generally you do not need to adjust the default configuration.
+ The default size (configured by `server.grpc-concurrency`) of the gRPC thread pool is `5`. This thread pool has almost no computing overhead and is mainly responsible for network I/O and deserialization requests, so generally you do not need to adjust the default configuration.
 
  - If the machine deployed with TiKV has a small number (less than or equal to 8) of CPU cores, consider setting the `server.grpc-concurrency` configuration item to `2`.
  - If the machine deployed with TiKV has very high configuration, TiKV undertakes a large number of read and write requests, and the value of `gRPC poll CPU` that monitors Thread CPU on Grafana exceeds 80% of `server.grpc-concurrency`, then consider increasing the value of `server.grpc-concurrency` to keep the thread pool usage rate below 80% (that is, the metric on Grafana is lower than `80% * server.grpc-concurrency`).