[SERVER-75874] Evaluate the feasibility of replacing the std::unique_ptr decorations with boost::optional decorations Created: 08/Apr/23 Updated: 21/Apr/23 Resolved: 21/Apr/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Vojislav Stojkovic | Assignee: | Alex Li |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Sprint: | Service Arch 2023-04-17, Service Arch 2023-05-01 |
| Participants: |
| Description |
|
When a decorable object is instantiated, the associated DecorationContainer allocates the necessary space for all the decorations at once. However, the codebase currently contains a large number of decorations whose type is a std::unique_ptr. This defeats the purpose of allocating all decorations together and introduces a performance penalty. We need to go over all of these decorations and evaluate the feasibility of changing their type from std::unique_ptr to boost::optional. |