Investigate performance penalty of change streams optimizations in "shard lite" configuration

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Minor - P4
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Query Execution
    • ALL
    • QE 2022-02-07
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      The change_streams_listen_throughput benchmark shows a roughly 7% performance loss in 5.2 (compared to 5.0) in the case where there is no `$match` stage to optimize.

      This tradeoff is reasonable in exchange for the substantial performance improvement available when `$match` can be optimized (especially considering that other variants show much less of a performance penalty), but it would be worthwhile to investigate the specifics of the loss and see if there are potential mitigations.

            Assignee:
            [DO NOT USE] Backlog - Query Execution
            Reporter:
            Justin Seyster
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: