-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Internal Code
-
None
-
Fully Compatible
-
ALL
-
Service Arch 2021-03-22
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 SERVER-52904. It would be good to get the benchmark in first to establish a baseline from which to evaluate the next changes for that ticket.
- is depended on by
-
SERVER-52904 Improve implementation of mongo::Status
- Closed