[SERVER-84283] Miscellaneous cleanup in router command path Created: 18/Dec/23  Updated: 05/Feb/24

Status: Open
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Jack Mulrow Assignee: Jack Mulrow
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Sprint: Cluster Scalability 2023-12-25, Cluster Scalability 2024-1-22, Cluster Scalability 2024-2-5, Cluster Scalability 2024-2-19
Participants:

 Description   

While profiling for invisible sharding performance, I noticed a few small things that can be improved in the router command path that likely won't move the needle but are simple to do:

  1. TrackingMetadata initializes an OID for every request, which increments an atomic, but doesn't use it unless tracking verbosity is on and the command uses a ShardRemote.
  2. Getting the connection string from a Shard type returns a copy and is used pretty often.
  3. The bulk write path maintains a map of written opTimes from ConnectionString to opTime, which is never used.

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