Store a hashed telemetry key rather than a BSONObj

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 7.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Query Optimization
    • Fully Compatible
    • QO 2023-05-15
    • 162
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

            Assignee:
            Davis Haupt (Inactive)
            Reporter:
            Charlie Swanson
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: