Backtrace for a simple aggregate operation has over 100 stack frames before hitting CommandInvocation::run()

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Server Programmability
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      I've noticed while doing some debugging lately that for simple queries (and presumably for all database commands), that there are a ton of promise/future-related stack frames above the CommandInvocation being run. I will attach an example backtrace that I collected recently (it's too long to fit in the ticket description).

      This isn't a problem per se, but I'm a bit surprised by the apparent level of complexity. It also seems like this can't be good for performance. Is there any room for improvement here?

            Assignee:
            Unassigned
            Reporter:
            David Storch
            Votes:
            1 Vote for this issue
            Watchers:
            14 Start watching this issue

              Created:
              Updated: