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

with new index skipping, nscanned may not accurately predict time cost of a query

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major - P3 Major - P3
    • 1.7.0
    • None
    • None
    • None
    • ALL

    Description

      With the new btree skipping implementation, currently nscanned counts the number of documents which match the query according to the index spec. But this can result in situations in which indexes which require skipping have the same nscanned as indexes not requiring skipping.

      One solution is to include in nscanned the number of btree entries touched during skipping. Currently there's no way to transfer that information from the btree implementation to the query optimizer, but that can be added.

      I can implement, but sounds like a good idea Eliot?

      Attachments

        Activity

          People

            aaron Aaron Staple
            aaron Aaron Staple
            Votes:
            1 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: