[SERVER-55056] benchmark the performance of the Status class Created: 09/Mar/21 Updated: 29/Oct/23 Resolved: 11/Mar/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Internal Code |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Billy Donahue | Assignee: | Billy Donahue |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Sprint: | Service Arch 2021-03-22 | ||||||||
| Participants: | |||||||||
| Description |
|
We care about the performance of Status, particularly the cost of making, copying, and destroying them, yet we have no benchmark to measure the speed of these operations. This is the first piece of |
| Comments |
| Comment by Githook User [ 11/Mar/21 ] |
|
Author: {'name': 'Billy Donahue', 'email': 'billy.donahue@mongodb.com', 'username': 'BillyDonahue'}Message: Also try variations of boost::intrusive_ptr behavior relevant to Status. |