[SERVER-8576] Identify opportunities to replace global data lock with finer grained locks. Created: 14/Feb/13 Updated: 06/Dec/22 Resolved: 04/Mar/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Concurrency |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Andy Schwerin | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Incomplete | Votes: | 2 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Storage Execution
|
||||
| Participants: | |||||
| Description |
|
Outcome of this task will be a list of improvement tickets that could be applied to the existing storage system, to reduce the number of code paths that require the global lock. They will be rated in terms of complexity and dynamic frequency (how much time in the field holding the global lock could be eliminated). |
| Comments |
| Comment by Sara Williamson [ 04/Mar/19 ] |
|
We have removed most instances, and the remaining will be tracked as individual tickets as we encounter them. |