explain() performance degraded when all potential plans added to results

XMLWordPrintableJSON

    • ALL
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      In a workload where explain() is called a lot I've lately seen a certain regression in throughput.
      I was able to isolate the commit that caused the problem.
      https://github.com/mongodb/mongo/commit/6dd40e54de4d62ed1c649f6f620a574e6de74fa8

      The throughput looks like 20% less and I'm completely able to recover if I revert to the previous revision. See screenshot attached.

        1. chart_2.png
          8 kB
          Davide Italiano

            Assignee:
            David Storch
            Reporter:
            Davide Italiano (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: