Skip to content

Transactions convenient api alignment #1898

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
tadjik1 wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Transactions convenient api alignment #1898

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
6a96826
Align backoff initial and growth value with actual formula.
tadjik1 Feb 18, 2026
7e8a80f
pluralize time units
tadjik1 Feb 18, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion source/transactions-convenient-api/transactions-convenient-api.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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-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.

Expand Down
Loading