From 0712df21732d50250f46d93bc7196ff217492a3c Mon Sep 17 00:00:00 2001 From: Aolin Date: Tue, 13 Aug 2024 19:00:47 +0800 Subject: [PATCH] Apply suggestions from code review --- tidb-configuration-file.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/tidb-configuration-file.md b/tidb-configuration-file.md index 8b2d5987a5b3a..6fbd5e7670bd0 100644 --- a/tidb-configuration-file.md +++ b/tidb-configuration-file.md @@ -728,12 +728,13 @@ Configuration items related to opentracing.reporter. ### `batch-policy` New in v8.3.0 -- Controls the batching strategy for requests from TiDB to TiKV. +- Controls the batching strategy for requests from TiDB to TiKV. When sending requests to TiKV, TiDB always encapsulates the requests in the current waiting queue into a `BatchCommandsRequest` and sends it to TiKV as a package. This is the basic batching strategy. When the load throughput is high, TiDB decides whether to wait for an extra period after the basic batching based on the `batch-policy` configuration item. This additional batching allows more requests to be encapsulated in a single `BatchCommandsRequest`. - Default value: `"standard"` - Value options: - `"basic"`: the behavior is consistent with versions before v8.3.0, where TiDB performs additional batching only if [`tikv-client.max-batch-wait-time`](#max-batch-wait-time) is greater than 0 and the load of TiKV exceeds the value of [`tikv-client.overload-threshold`](#overload-threshold). - `"standard"`: TiDB dynamically batches requests based the arrival time intervals of recent requests, suitable for high-throughput scenarios. - `"positive"`: TiDB always performs additional batching, suitable for high-throughput testing scenarios to achieve optimal performance. However, in low-load scenarios, this strategy might introduce unnecessary batching wait time, potentially reducing performance. + - `"custom{...}"`: you can customize the batching strategy parameters. It is not recommended to set this value option. ### `max-batch-size`