storage,kv: improve the performance intent resolution over a key range #66900
Labels
C-enhancement
Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)
C-performance
Perf of queries or internals. Solution not expected to change functional behavior.
N-followup
Needs followup.
O-postmortem
Originated from a Postmortem action item.
T-storage
Storage Team
Now that we have introduced a separated lock table in #41720. We can significantly improve intent resolution for transactions
that write many intents such that we track intent ranges. This can result in close to 100x performance improvement in range intent resolution.
Epic: CRDB-8282
The text was updated successfully, but these errors were encountered: