[SERVER-76354] Modify ConcurrentSharedValuesMap to use immutable maps Created: 20/Apr/23 Updated: 21/Apr/23 Resolved: 20/Apr/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Jordi Olivares Provencio | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Storage Execution
|
||||||||
| Participants: | |||||||||
| Description |
|
ConcurrentSharedValuesMap currently uses a shared_ptr that's replaced with another one whenever we update the map. Updates to the map happen by copying the entire map and replacing the specified element. This is a pattern that lends itself very easily to our new immutable unordered_map. |
| Comments |
| Comment by Jordi Olivares Provencio [ 20/Apr/23 ] |
|
Wrongly opened two tickets |