[SERVER-54614] Introduce striped lock to BucketCatalog to improve throughput Created: 18/Feb/21 Updated: 27/Feb/21 Resolved: 27/Feb/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Dan Larkin-York | Assignee: | Dan Larkin-York |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Sprint: | Execution Team 2021-02-22, Execution Team 2021-03-08 | ||||||||
| Participants: | |||||||||
| Description |
|
In many-writer, large-batch timeseries workloads, a great deal of time is spent waiting on the mutex while we do read-only operations on shared data structures. We can introduced a striped (i.e. sharded, partitioned) mutex to support this in a way that allows multiple concurrent readers, but still allows an operation to take an exclusive lock (by locking all stripes) to perform a write. |
| Comments |
| Comment by Githook User [ 26/Feb/21 ] |
|
Author: {'name': 'Dan Larkin-York', 'email': 'dan.larkin-york@mongodb.com', 'username': 'dhly-etc'}Message: |