[SERVER-45850] Remove mutex guards on read access for _shardId and _clusterId in ShardingState Created: 29/Jan/20 Updated: 29/Oct/23 Resolved: 05/Feb/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.4 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Blake Oler | Assignee: | Blake Oler |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Sprint: | Sharding 2020-02-10 | ||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
The ShardingState mutex guard for data read access on these variables is unnecessary, due to existing invariants that:
Removing these read access mutex acquisitions will reverse the performance drop found in BF-16012. |
| Comments |
| Comment by Githook User [ 05/Feb/20 ] |
|
Author: {'username': 'BlakeIsBlake', 'name': 'Blake Oler', 'email': 'blake.oler@mongodb.com'}Message: |