-
Type:
Improvement
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Catalog and Routing
-
Fully Compatible
-
v8.0
-
CAR Team 2024-04-29, CAR Team 2024-05-13
-
200
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
-
None
CollectionCatalog::latest performs an atomic_load on a shared_ptr, which looks like it is a simple atomic load operation but instead has to use a global mutex to coordinate the shared_ptr's refcount update with the pointer update. This shows up when profiling acquireCollection (PERF-5353)
- has to be done before
-
-
- Open
-
- is duplicated by
-
SERVER-56428 Replace usage of atomic_load/atomic_store of shared_ptr or custom mutex with atomic<shared_ptr>
-
- Backlog
-