[SERVER-79187] Investigate the performance impact of using NamespaceString::dbName Created: 21/Jul/23  Updated: 09/Aug/23  Resolved: 09/Aug/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.1.0-rc0

Type: Task Priority: Major - P3
Reporter: Sophia Tan Assignee: Mathis Bessa
Resolution: Done Votes: 0
Labels: ntdi_must_have
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-79074 Replace NamespaceString::db() with Na... Closed
Related
is related to SERVER-79806 KeysCollectionClientDirect::_insert t... Closed
Assigned Teams:
Serverless
Backwards Compatibility: Fully Compatible
Sprint: Server Serverless 2023-08-07, Server Serverless 2023-08-21
Participants:
Story Points: 2

 Description   

Today, `NamespaceString::db()` is used for serialization the db names. It does not work correctly for commands serialization/deserialization. If we replace it with `DatabaseNameUtil::serialize(nss.dbName())` directly, performance regression can be observed.
In this task, we should investigate how to avoid performance regression by creating a prototype and test the performance with it.


Generated at Thu Feb 08 06:40:18 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.