pingcap / pingcap/tidb

Lost performance when locking untouched keys

Open
#44,332 0 comments 0 reactions 0 assignees View on GitHub
sig/transaction type/enhancement
Dominant language
Go
Stars
40.5k
Forks
6.2k
PR merge metrics
PR metrics pending

Description

## Enhancement

In the fix #42210, we lock some untouched keys, and there may be high contention when there are conflict on untouched keys, because we don't lock them before, the performance is decreased.

Maybe we can optimize the performance for locking untouched keys if TiDB support a share-exclusive lock, only share lock is required for such case.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.