ExportXMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • 9.1.0-rc0, 9.1.0-rc1022
    • Affects Version/s: None
    • Component/s: None
    • None
    • Query Execution
    • Fully Compatible
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Currently, index bounds checks are done on BSON in both classic and sbe. For both engines this is inefficient. SBE should try to avoid materializing BSON as much as possible. In Classic ixscan, materializing the BSON in an index scan is often unnecessary, since there may be a FETCH that only requires the RecordId

      Once bounds checking is done as keystrings, SBE will not have to materialize BSON, and Classic can lazily materialize the BSON. This saves significant work and has shown up to 30% lower latency in benchmarks

            Assignee:
            Matt Boros
            Reporter:
            Matt Boros
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: