[SERVER-54516] Introduce finer-grained locking in BucketCatalog and tighten critical sections Created: 12/Feb/21 Updated: 01/Apr/21 Resolved: 20/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 | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 138 | ||||||||||||
| Description |
|
Currently for the timeseries insert path, when we have many writers and large batches, we spend a great deal of time waiting on the monolithic BucketCatalog mutex. We should make an effort to shrink our critical sections and possibly move to finer-grained locking within the BucketCatalog operations. |
| Comments |
| Comment by Githook User [ 20/Feb/21 ] |
|
Author: {'name': 'Dan Larkin-York', 'email': 'dan.larkin-york@mongodb.com', 'username': 'dhly-etc'}Message: |