[IGNITE-21379] Investigate whether currently used busyLocks implementation is fast enough

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Labels: ignite-3 performance
• Release Note: There is no change needed by the result of the investigation.
• Epic Link: performance enhancement
• Assignee: Vladislav Pyatkov
• Reporter: Alexander Lapin
• Created: 29/Jan/24 14:48
• Updated: 15/Feb/24 07:46
• Resolved: 15/Feb/24 07:46

Description

Motivation

Seems that our busyLocks (IgniteSpinBusyLock) aren't good enough from the performance perspective. Let's compare current implementation with common RW locks, CheckpointReadWriteLock, etc. Depending on the results it'll be required either to use faster implementation or re-consider busyLock idea itself because currently it brings significant performance drop. Given ticket is only about initial step - busyLock performance investigation.

Definition of Done

• Prepare JMH benchmarks for busyLocks performance investigation.
• Compare IgniteSpinBusyLock, common RW lock, CheckpointReadWriteLock, etc in order to understand whether IgniteSpinBusyLock is fast enough.

Issue Links

• is depended upon by: IGNITE-21378 Investigate whether it's possible to make txnState local map updates faster