From 4b41a7393e79d895050e1fd2610384c8124bca19 Mon Sep 17 00:00:00 2001 From: Ti Chi Robot Date: Sun, 26 Sep 2021 16:12:49 +0800 Subject: [PATCH] Tune TiKV: change the default value of `grpc-concurrency` (#6531) (#6544) --- tune-tikv-thread-performance.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tune-tikv-thread-performance.md b/tune-tikv-thread-performance.md index 0774e9b5f8859..05392956349dc 100644 --- a/tune-tikv-thread-performance.md +++ b/tune-tikv-thread-performance.md @@ -36,7 +36,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`).