[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:
Depends
is depended on by SERVER-52904 Improve implementation of mongo::Status Closed
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 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.

Example:
https://docs.google.com/spreadsheets/d/1BLHZhlWmt-DPNvM6KDd9c3DyGrPqWRVbrep8LAZg7KM/edit#gid=1897039357



 Comments   
Comment by Githook User [ 11/Mar/21 ]

Author:

{'name': 'Billy Donahue', 'email': 'billy.donahue@mongodb.com', 'username': 'BillyDonahue'}

Message: SERVER-55056 benchmark for Status

Also try variations of boost::intrusive_ptr behavior relevant to Status.
Branch: master
https://github.com/mongodb/mongo/commit/e3c74559769e07e6c9ddf67bc65d583ae7273b66

Generated at Thu Feb 08 05:35:19 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.