From 6a968268bd3b39f4f9f621efe24feeea84ba2bf4 Mon Sep 17 00:00:00 2001 From: Sergey Zelenov Date: Wed, 18 Feb 2026 15:47:01 +0100 Subject: [PATCH 1/2] Align backoff initial and growth value with actual formula. --- .../transactions-convenient-api/transactions-convenient-api.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/transactions-convenient-api/transactions-convenient-api.md b/source/transactions-convenient-api/transactions-convenient-api.md index 025fe4a939..24e2ed0d18 100644 --- a/source/transactions-convenient-api/transactions-convenient-api.md +++ b/source/transactions-convenient-api/transactions-convenient-api.md @@ -396,7 +396,7 @@ Previously, the driver would retry transactions immediately, which is fine for l server load increases, immediate retries can result in retry storms, unnecessarily further overloading the server. Exponential backoff is well-researched and accepted backoff strategy that is simple to implement. A low initial backoff -(1-millisecond) and growth value (1.25x) were chosen specifically to mitigate latency in low levels of contention. +(5-millisecond) and growth value (1.5x) were chosen specifically to mitigate latency in low levels of contention. Empirical evidence suggests that 500-millisecond max backoff ensured that a transaction did not wait so long as to exceed the 120-second timeout and reduced load spikes. From 7e8a80f26e82ff2104a11594f2d4b10019953ed4 Mon Sep 17 00:00:00 2001 From: Sergey Zelenov Date: Wed, 18 Feb 2026 15:48:54 +0100 Subject: [PATCH 2/2] pluralize time units --- .../transactions-convenient-api/transactions-convenient-api.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/transactions-convenient-api/transactions-convenient-api.md b/source/transactions-convenient-api/transactions-convenient-api.md index 24e2ed0d18..b4d4a16124 100644 --- a/source/transactions-convenient-api/transactions-convenient-api.md +++ b/source/transactions-convenient-api/transactions-convenient-api.md @@ -396,7 +396,7 @@ Previously, the driver would retry transactions immediately, which is fine for l server load increases, immediate retries can result in retry storms, unnecessarily further overloading the server. Exponential backoff is well-researched and accepted backoff strategy that is simple to implement. A low initial backoff -(5-millisecond) and growth value (1.5x) were chosen specifically to mitigate latency in low levels of contention. +(5-milliseconds) and growth value (1.5x) were chosen specifically to mitigate latency in low levels of contention. Empirical evidence suggests that 500-millisecond max backoff ensured that a transaction did not wait so long as to exceed the 120-second timeout and reduced load spikes.