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

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

    • Type: Icon: Improvement Improvement
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None
    • Service Arch

      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:
            backlog-server-servicearch [DO NOT USE] Backlog - Service Architecture
            Reporter:
            david.storch@mongodb.com David Storch
            Votes:
            1 Vote for this issue
            Watchers:
            13 Start watching this issue

              Created:
              Updated: