Optimize creation of min/max maps in extractCellBlocks()

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Minor - P4
    • 8.1.0-rc0, 8.0.0-rc7
    • Affects Version/s: None
    • Component/s: None
    • None
    • Query Integration
    • Fully Compatible
    • v8.0
    • QI 2024-05-13, QI 2024-05-27, QI 2024-06-10
    • 200
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      This was a suggestion from Henrik during code review:

      I think the server always store the data under min/max in the same order as they are stored under data. I see that we create two temporary maps to map the things together. Not sure how much we care but I believe it is possible to do this in the order they appear in BSON (plus a fallback if they do not). Would save you some allocations per bucket.

              Assignee:
              Chris Wolff
              Reporter:
              Chris Wolff
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: