Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-85812

Consider making bounds direction checking code debug only

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • None
    • Query Optimization

    Description

      In the LargeIndexedIn workload, 15% of total CPU time is spent in isValidFor(), which validates that the index bounds are in the correct order relative to the scan and index direction (for example, the bounds [1,3] is valid for ascending index + forward traversal and descending index + backwards traversal). isValidFor() is invoked immediately after aligning the bounds to satisfy the proper direction, and only used to log and tassert if it fails.

      Given the cost in a high-value workload, we should consider disabling this check in release builds.

      Attachments

        Activity

          People

            backlog-query-optimization Backlog - Query Optimization
            ben.shteinfeld@mongodb.com Ben Shteinfeld
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated: