-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Query Optimization
-
Fully Compatible
-
QO 2023-05-15
-
162
The design doc says we will be hashing it, and it is important to do this to understand the releasable performance numbers. It should reduce contention on the partitioned telemetry store mutex since comparisons will be simpler and probably faster, although it is a tradeoff since we are then adding a hash function invocation to the "hot path" at query time.
- depends on
-
SERVER-73152 Literal and field name redaction for aggregate command
- Closed
- duplicates
-
SERVER-76526 Remove cached redacted query from TelemetryMetrics
- Closed
- is related to
-
SERVER-75658 Investigate 14% regression in mixed_findOne from telemetry
- Closed
-
SERVER-75661 Investigate 13% regression in insert_jfalse_wmajority
- Closed