Uploaded image for project: 'Node.js Driver'
  1. Node.js Driver
  2. NODE-1305

Document potential performance degradation when using change streams

XMLWordPrintableJSON

    • Type: Icon: Improvement Improvement
    • Resolution: Unresolved
    • Priority: Icon: Minor - P4 Minor - P4
    • None
    • Affects Version/s: None
    • Component/s: Native
    • Labels:
      None

      The current pool implementation starts with a small poolSize, which limits the number of concurrent connections available. Each change stream created will tie up one of these connections completely while waiting on getMore commands, effectively clogging up the pools for other operation if the poolSize is small. We should document this so it's not a surprise to users, and they know how to mitigate the issue in the future.

      NOTE: We should also consider a potential future where we track these connections in a special queue just for change streams and tailable cursors.

            Assignee:
            Unassigned Unassigned
            Reporter:
            matt.broadstone@mongodb.com Matt Broadstone
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: