Use snapshot transactions in our bindings for read-only retry loops.
Open
- Dominant language
- C++
- Stars
- 16.7k
- Forks
- 1.6k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 126
Description
In some of our bindings, we have read-only transaction retry loops. It may be the case that passing a snapshot transaction rather than a regular transaction to these retry loops would provide a performance benefit.
It would probably be interesting to measure the effect of this optimization as well.
Contributor guide
Research direction
No files, tests, or specific bindings are named. Start by locating the bindings that implement read-only transaction retry loops, then compare snapshot and regular transactions and measure the performance effect; done means the affected loops are identified, the optimization is justified by measurements, and the relevant bindings are updated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- databases
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100